|
Yes,
it's YOUR data. Even if you're using CMP EBs, you can still compress your data,
assuming you also decompress it accordingly. BUT,
1) You
will lose search capabilities in the Persistance layer (a SQL query won't
support compression)
2)
Performance gains depend on the network (latency, bandwidth, availability)
between the different parts of your application. On most applications this isn't
generally true. Performance gains are simply the difference between
compression/decompression time vs. network conditions and round-trips. It's
impossible to even guess the scenario from the data you
provide.
3) Your diagram seems to implicate the client has
direct access to the DAO, thru the use of value objects. Why the EJBs
then?
Perhaps if you could explain
more....
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
