|
Why
compress anything? What does it accomplish?
How is
it an object stream? Do you mean an java.io.ObjectOutputStream
?
If
that's the case, just make sure the stream goes into a holder that is either
Serializable or a primitive (for instance use
java.io.ByteArrayOutputStream, then extract the byte
array).
Check
the java docs for implications and considerations about it (interface is
java.io.Serializable). Also check out the RMI
documentation.
By all
means comment on why you want to compress an entity, and then decompress it on
the client (which, I'm presuming, will benefit from a superb network connection
to the App Server). Based on data I have, I think it'll negatively impact on
performance. The rationale behind the design choice has me
intrigued.
Also,
I'm posting this directly to EJB-INTEREST as I think the other post didn't make
it to the list.
Juan Pablo Lorandi
Chief Software
Architect
Code Foundry Ltd.
Barberstown, Straffan, Co. Kildare, Ireland. Tel: +353-1-6012050 Fax: +353-1-6012051 Mobile: +353-86-2157900 www.codefoundry.com
|
Title: Message
- Compression API in EJB SAMINATHAN
- Re: Compression API in EJB Juan Pablo Lorandi
- Re: Compression API in EJB Juan Pablo Lorandi
- Re: Compression API in EJB David Jones
- Re: Compression API in EJB SAMINATHAN
- Re: Compression API in EJB Juan Pablo Lorandi
- Re: Compression API in EJB Richard S.Martin
- Re: Compression API in EJB Juan Pablo Lorandi
- Re: Compression API in EJB SAMINATHAN
- Re: Compression API in EJB Juan Pablo Lorandi
