You are right :-(

Igor

----- Original Message ----- 
From: "Filip Hanik - Dev" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Friday, October 01, 2004 5:31 PM
Subject: Re: Synchronization in cluster


> cause if you have two servers, two different sessions can perform upload
in two different VMs.
> He never said there is only one session doing upload, he was asking for a
distributed lock
>
> Filip
>
> ----- Original Message ----- 
> From: "Ralph Einfeldt" <[EMAIL PROTECTED]>
> To: "Tomcat Users List" <[EMAIL PROTECTED]>
> Sent: Friday, October 01, 2004 7:36 AM
> Subject: RE: Synchronization in cluster
>
>
>
> Why not ?
>
> As I understood the static variable holds the information for the
> current upload.
>
> If the session is sticky the user will stay in the same jvm
> and see the same static variable with each refresh.
>
> I just see some downsides:
> - if you want to assure that the downloads are serialised you have
>   to implement a locking mechanism.
> - you loose the central point to see all states at the same time.
> - if the instance that performs the update dies, the user will
>   get to an instance that doesn't know anything about the download.
>
> > -----Original Message-----
> > From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED]
> > Sent: Friday, October 01, 2004 1:51 PM
> > To: Tomcat Users List
> > Subject: RE: Synchronization in cluster
> >
> >
> > That doesn't solve the problem
> >
> > -----Original Message-----
> > From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]
> > Sent: Friday, October 01, 2004 4:26 AM
> > To: Tomcat Users List
> > Subject: RE: Synchronization in cluster
> >
> >
> >
> > With this usage scenario i would recommend sticky sessions.
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to