Thanx for the reply Julia .... 

What about load-balancing and scalability .... i havent fully experimented with 
Servlet/EJB architecture ..
we dont mind doing away with ND but we expect a pretty heavy load on the app and im 
not sure how
easy it is to scale using Servlets/EJB ....

"Julia Martinson" <[EMAIL PROTECTED]> wrote:
>><[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...>> We plan
         on adopting EJB architecture and we want to know how we can>> manage session 
info
         in EJB SessionBeans.  In other words what is the>> EJB equivalent of 
putUserSessionObject().
          We understand the architecture>>  is different (session beans reside on the 
server,etc),
         but how do we make>> sure individual customers access only their own info and 
the
         server should recognize>>  individuals i.e. persistence.>>Standard way of 
keeping
         client-related info for stateless clients (browser) is>storing it in 
HTTPSession
         object. If you are using servlets or JSP you can initialize>HTTP Session with 
first
         request and all subsequent requests will include>unique identifier for this 
client's
         session (often cookies) . ND does something>similar but they have their own 
Session
         object from spider framework.>I guess if you don't want to use spider classes 
you
         might want to reevaluate your>decision to use ND and just use standard 
servlet/JSP
         + EJBs framework which>is now supported by many application 
servers.>>>-->[EMAIL PROTECTED]>>>>
_________________________________________________________________________

For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html

For dire need help, email: [EMAIL PROTECTED]

Reply via email to