Title: Message
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
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]] On Behalf Of SAMINATHAN
Sent: Monday, April 15, 2002 10:36 AM
To: [EMAIL PROTECTED]
Subject: Compression API in EJB

Hi all
 
    I would like to know whether compression of object in EJB is allowed or not.Though am not directly  going to use inside the bean.
   
     For example i have the follwoing architecture
 
Client -----> SLSB -----> EB -----DAO -----DB
    |                                          |
    |                                          | 
    |--------------------->VALUE OBJECT
 
 
 on Form load my ejbSelect will return me the value object.Since in my case it is a BMP my DAO's select method
will return me the value object and i want to compress that  before sending to  entity --- Session and in the client code i will decompress
and use it.Note am not doing any compression in my bean.
 
And by doing this , will  my performance and response time improve?
 
Is there any  known or unknown implication there in this?
 
Thanks and Regards
Saminathan.
 
 
  

Reply via email to