[Seaside] REST and Seaside

[Nevin Pratt]

>Ok, 1500 concurrent sessions is a very big number; that's pretty
>consistent with your image sizes, so I agree it probably doesn't have
>anything to do with GLORP etc.  But even with a 100 minute time out
>that sounds awfully high; do you really think you get, say, 10000
>visitors per day?  Or is something else going on?  Either the peaks
>are very, very heavy, or there's something wrong with the expiry.
>  
>

I don't know.  I know that most of the days orders come in between 8:00 
AM and 1:00 PM.  So they do tend to cluster up around a particular time 
span.

>One instrumentation that would help here would be to simply log every
>time a session is created.  That should barely affect performance and
>would be a good indication of what's going on.
>
>  
>
>> I might have gotten hit with a DOS attack or something on Thursday and
>>Friday, I don't know.  The traffic numbers certainly would seem to support
>>that possibility.
>>    
>>
>
>Yes.  I wonder what strategies we can use to detect and cope with
>that.  One I can think of is to link the expiry time  to how much the
>application has been used: if all you do is request the homepage, your
>session will expire very quickly, but if you look around a little more
>you're given more time.  That seem reasonable?
>
>
>  
>

I think that's a great idea.

Nevin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20050409/9eef1ac7/attachment.htm