Hi Christian, by using Trace I think I found the reason for the strange effect. I'm using CURL.FormAddKeyContainerContentTyp to upload my assets. As the container field contains 5 types (DPI_, FNAM, JPEG, PDF , SIZE) the function tries to upload all 5 of them as 5 streams (see below).
MBS Plugin called with 6 parameters. Parameter 0: "CURL.FormAddKeyContainerContentType" Parameter 1: 1.000000 Parameter 2: "Filedata" Parameter 3: "AuWI_im_Digitaldruck_EFI.pdf" Parameter 4: Binary Data with 5 streams, 15720513 Bytes in total: DPI_ "....", FNAM "image:AuWI_im_Digitaldruck_EFI.pdf", JPEG "......JFIF.....H.H......AppleMark.......................................... % ..#...!,!#'(***...1-)1%", PDF "%PDF-1.6.%......1440 0 obj.<</Filter/FlateDecode/First 493/Length 967/N 56/Type/ObjStm>>stream....y", SIZE 720 x 540 Parameter 5: "PDF " ErrorCode 0 (no error), Result: "OK" How can I prevent this? I thought using "PDF " (with a trailing space as the original type is written) would select what type should be uploaded. Regards, Robert Am 22.05.13 17:46 schrieb "Christian Schmitz" unter <[email protected]>: > > Am 21.05.2013 um 14:39 schrieb Robert Zacherl <[email protected]>: > >> Hello, >> >> Everything works fine as long as the asset's file size doesn't exceed a >> certain limit (I'm not sure yet where this limit is but it's definitely >> somewhere between 5 and 15 MB). > > Can you enable Trace and see what parameters you pass to functions? > Also use CURL.SetOptionVerbose to get debug messages collected. > What result does Perform method give you? > > For me a 50 MB upload is not an issue from a file or container. > >> I'm aware that the CURL component offers a couple of function which >> influence the size of certain CURL options like e.q. SetOptionMaxFileSize >> or SetOptionMaxFileSizeLarge (btw what is the difference between the two?) > > large is for 64bit, other for 32bit file sizes. > > But I'll change that for 3.3 release, so we internally always use the large > method. > Also I'll change OpenInputFile function to query file size and pass it to > curl, so we can better show progress. > >> The strange thing >> is that the correct amount of data for each uploaded file arrives at the DAM >> server but the whole data only consists only of zero bytes. > > That sounds very strange. > > > > Greetings > Christian > > -- > Read our blog about news on our plugins: > > http://www.mbsplugins.de/ > > _______________________________________________ > Mbsfmplugin_monkeybreadsoftware.info mailing list > [email protected] > https://ml01.ispgateway.de/mailman/listinfo/mbsfmplugin_monkeybreadsoftware.in > fo > _______________________________________________ Mbsfmplugin_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsfmplugin_monkeybreadsoftware.info
