Bill,
That is really interesting.
Furthermore, for BEA, remember that thanks to their front-end dispatcher, it
is always the same server that will receive the invocations (until it
fails). Consequently, they don't need distributed locking because until a
server dies, there is no distributed state anyway (I mean state that is used
on different nodes, state is only replicated but replicas are not used)
Cheers,
Sacha
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de Bill
> Burke
> Envoy� : vendredi, 28 d�cembre 2001 22:14
> � : Jboss-Development@Lists. Sourceforge. Net
> Objet : [JBoss-dev] HttpSessions: distributed locking
>
>
> Weblogic doesn't seem to support concurrent access to clustered
> HttpSessions. Maybe it is all right for us to be this lazy too.
>
>
> Applications Using Frames Must Coordinate Session Access
>
> If you are designing a Web application that utilizes multiple frames, keep
> in mind that there is no synchronization of requests made by frames in a
> given frameset. For example, it is possible for multiple frames in a
> frameset to create multiple sessions on behalf of the client application,
> even though the client should logically create only a single session.
>
> In a clustered environment, poor coordination of frame requests can cause
> unexpected application behavior. For example, multiple frame requests can
> "reset" the application's association with a clustered instance,
> because the
> proxy plug-in treats each request independently. It is also
> possible for an
> application to corrupt session data by modifying the same session
> attribute
> via multiple frames in a frameset.
>
> To avoid unexpected application behavior, always use careful planning when
> accessing session data with frames. You can apply one of the following
> general rules to avoid common problems:
>
>
> In a given frameset, ensure that only one frame creates and
> modifies session
> data.
>
> Always create the session in a frame of the first frameset your
> application
> uses (for example, create the session in the first HTML page that is
> visited). After the session has been created, access the session data only
> in framesets other than the first frameset.
>
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
