[Seaside] Re: Concurrent requests from multiple sessions
Sven Van Caekenberghe
sven at stfx.eu
Tue Mar 10 11:12:08 UTC 2015
> On 10 Mar 2015, at 11:15, wilwarin <Ondrej.Altman at seznam.cz> wrote:
> ( I tried Sven's code and it is possible to do another work during waiting,
> it is OK. )
Does it also work (slowly) during the benchmark ?
That simulates your 'long running work'.
>> But that problem (not being able to process concurrent requests) is
>> certainly not inherent to Seaside or Pharo. If that were the case we
>> should all stop using it.
> Hopefully I understand, so it is not the case. If I am correct, it means
> that in Seaside it is necessary to solve similar situations with different
> access. In case of for example difficult server-side calculation (or
> processing of big amount of data), we have to count on a possible problem
> with concurrent requests from multiple sessions. Am I right? Or, if not,
> where could the problem lay?
What everybody here tries to explain to you is that the problem is most probably in your DB driver (in Smalltalk or further down): it probably cannot do more than one concurrent request (as it is currently implemented). That is not a Seaside nor a fundamental Smalltalk problem.
Try investigating that aspect, separate from Seaside.
More information about the seaside