Why not simply keep client state in the client itself? Since you have a "fat
client" you might was well use its RAM!
-Chris.
> -----Original Message-----
> From: Paul Nicklin [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, January 24, 2000 5:22 AM
> To: [EMAIL PROTECTED]
> Subject: Equivalent of HTTPSession for an Java Application client
>
> I'm currently builing a Java client application using EJBs in the server.
> I have to store information about the currently connected user, and I
> can't find
> a useful vehicle - I thought that the session context would work, but a
> new one
> is created per 'use' of the bean. If this were an HTTP (web page/JSP etc)
> then I
> could carry this info on the HTTP Session object, is there an equivalent
> object
> that 'follows' a particular connected client?
> What is the alternative?
>
> Paul.
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
