Hi:
We are trying to develop a remote cache server. Our goals is to reduce memory consumption (and GC cycles) in our app server and share the common read-only data across multiple servers. .We have experimented with RMI and EJB-based solutions. The RMI solution seems to work. However, we are running into trouble with the EJB solution. We are using Websphere 4.0. for the EJB-based approach
First we tried to use a stateful session bean, but soon we discovered that it would only work for a given client, not as a general purpose cache. Now we are trying to use entity beans, but the container does not give us the same bean instance. It creates a new bean instance which defeats the purpose of using the bean as a cache server. We are passing the reference to the bean between different clients using the EJBHandle serialized in LDAP (not calling EJBCreate or EJBFind).
Do we have a chance of making the EJB solution work, or should we drop this approach and stay with the RMI solution?
Thanks in advance for the help.
Kamyar
Do you Yahoo!?
Free online calendar with sync to Outlook(TM). --- You are currently subscribed to jdjlist as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] http://www.sys-con.com/fusetalk
