[Seaside] Re: Concurrent requests from multiple sessions

[Bob Arning]

BTW, did you include some code in your message? I didn't see any if you did.


On 3/10/15 9:25 AM, wilwarin wrote:
>> I got the impression that he suggests there is a fundamental
>> problem with something except his own code.
> Then I have to apologize, it really was not meant to be offensive. I just
> wanted to know, whether the issue we are facing is standard or not. That's
> why I was asking for correction of my words. Sorry.
>
>> Well, we can't help him unless he give us a reproducible case.
> In the end I tested a really simple component:
>
>
>
> Then the link was clicked from two different sessions simultaneously. And
> now it is the time, when I have to admit I was quite wrong (problem with my
> code). During first comparisons, the 'getResults' part was called during the
> rendering (between those two DIVs), and results (in both VAST and Pharo)
> were like following:
>
>
>
> --- BTW: ---
>> Your rendering method is just for painting the current state of your
>> component, it shouldn’t be concerned with changing that state.
> So, when somebody does some data processing during the rendering, it will
> cause this problem?
> -------------
>
> => Now, after several changes it looks like we still have this problem with
> a component above only in VAST.
>
>
>
> --
> View this message in context: http://forum.world.st/Concurrent-requests-from-multiple-sessions-tp4809929p4810964.html
> Sent from the Seaside General mailing list archive at Nabble.com.
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

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