I guess I didn't explain this very well in my original post, so I need
to make a clarification here.

We don't want to share information between client sessions.  Each
client session will have it's own set of  data to be cached.  This
is why I was thinking that we'd need stateful  session beans.  In
one of the replies, someone mentioned using a Servlet
and the Session object to associate data with a given client.
This would appear to be less "expensive" than using the stateful
session bean  approach (I assume), but what other issues would be
involved with this servlet/Session object approach?

Thanks,
Jeff

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to