[Seaside] ThreadPool with Seaside - how?
jtuchel at objektfabrik.de
Wed Jul 26 12:04:12 UTC 2017
I guess you should simply avoid accessing the session in the forked process for now.
Not sure I fully understand what Philippe tried to explain, but I can confirm I never saw any problems when using teh current Seaside component for objects to be used in a background process...
> Sabine Manaa <manaa.sabine at gmail.com> hat am 26. Juli 2017 um 12:09 geschrieben:
>  Paul and Ramon suggested to use the ThreadPool  to me.
> I want to replace my forked code for generating reports with it.
> When trying to use it within my seaside application, I have a problem.
> I reduced the Problem to this:
> -> this works, a simple in inspector pops up
> html mdlButton
> onClick: (html jQuery ajax script: [ :script | [ #simple inspect ] queueWork ]);
> with: '0'.
> -> this does not work.
> The generation of my reports needs the sessions objects.
> Also, calling another method of the session does not work.
> html mdlButton
> (html jQuery ajax
> script: [ :script | [ self session inspect ] queueWorkAndExpireIn: 25 seconds session: self session ]);
> with: '1'
> Did I miss something?
> Paul, thank you for updating  a few days ago
>  http://forum.world.st/immediate-display-alert-to-user-while-Ajax-request-td4956083.html#a4956534 http://forum.world.st/immediate-display-alert-to-user-while-Ajax-request-td4956083.html#a4956534
>  http://onsmalltalk.com/2010-07-28-a-simple-thread-pool-for-smalltalk
> http://smalltalkhub.com/#!/~pdebruic/ThreadPool/packages/ThreadPool http://smalltalkhub.com/#!/~pdebruic/ThreadPool/packages/ThreadPool
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside