I am working on a project where we need to repeatedly authenticate access
to a session bean method. Due to some technical restrictions we can't use
cookies to authenticate a session. Some piece of client software may need
to access the same session bean method a hundred times in a row, but we
have no way of knowing (from the server side) whether or not those
requests are coming from the same client. There also may be many clients
accessing the same method at the same time.
Username and password information is stored in a database. Would it
significantly increase performance to represent the username/password
information with an entity bean so that the container can cache that
information instead of making a trip to the db each time?
Anyone else out there had to solve a similar problem?
-M@
--
Matt Hixson
Aventail Corporation
Seattle, Washington
www.aventail.com
===========================================================================
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".
