Is Seaside responsive to other users while it serves one user? Esp. during Fileupload?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Is Seaside responsive to other users while it serves one user? Esp. during Fileupload?

Helene Bilbo
Hi,

if i allow uploading files, and someones upload takes lets say 10 minutes - when somebody else tries to connect to my seaside application during this 10 minutes, does it respond? Or can it serve only one user at a time?

Best regards, helene.
Reply | Threaded
Open this post in threaded view
|

Re: Is Seaside responsive to other users while it serves one user? Esp. during Fileupload?

Philippe Marschall
On Thu, May 10, 2012 at 3:58 PM, Helene Bilbo
<[hidden email]> wrote:
> Hi,
>
> if i allow uploading files, and someones upload takes lets say 10 minutes -
> when somebody else tries to connect to my seaside application during this 10
> minutes, does it respond? ...

It should, in theory. Specifics depend on the platform. A gem can
handle only one request at a time, but you can have several gems.

> Or can it serve only one user at a time?

The same session can only be accessed at a time.

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Is Seaside responsive to other users while it serves one user? Esp. during Fileupload?

Helene Bilbo
Philippe Marschall wrote
On Thu, May 10, 2012 at 3:58 PM, Helene Bilbo
<[hidden email]> wrote:
> if i allow uploading files, and someones upload takes lets say 10 minutes -
> when somebody else tries to connect to my seaside application during this 10
> minutes, does it respond? ...

It should, in theory. Specifics depend on the platform. A gem can
handle only one request at a time, but you can have several gems.
i wanted to install one single seaside-pharo (zinc server) image on linode behind an apache server.