Hi Mark, With ULC you cannot switch the carrier stream per request, you can only set it once per application. However you could write your own "Filer extension" for ULC which conceptually does the following (assuming you upload the corresponding file to server): 1) The client reads in the file via a zipping stream and buffers it. 2) Then it sends resulting buffered, zipped byte array to the server. 3) The server unzips the resulting byte stream for further processing. (You would use the regular way for writing extensions, meaning subclassing UIProxy and ULCProxy.)
Hope this helps. Greetings, Daniel -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of markee Sent: Montag, 17. Juli 2006 17:07 To: [EMAIL PROTECTED] Com Subject: Re: [ULC-developer] Improving performance when sending bytes in 6.1 On 17 Jul 2006, at 10:29, Daniel Pfeifer wrote: > Hi Mark, > > according to our own experience, zip-compression is very CPU > intensive. > For ULC, you can turn off zip-compression for client-server > communication. > This will reduce the CPU load but obviously the message size will > become > larger. Section 4.5 of the ULC Extension Guide explains, how you can > turn off zip-compression -> you should use the > "TrivialCarrierStreamProvider" > in this case. Turning off Canoo compression and using Java SPEED compression makes our code faster, but we also have a Filer which uploads a files which is now slower. Can we tell whether Canoo's compression is set programatically and can we control it on a transaction basis. MArk _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer _______________________________________________ ULC-developer mailing list [email protected] http://lists.canoo.com/mailman/listinfo/ulc-developer
