[Seaside] Concurrent Programming

[Sebastian Sastre]

why the fork that way?

I’d think more into make it a normal render page that has a little piece of javascript that will do an ajax hit to a server callback to do whatever you want, no?




> On Feb 27, 2015, at 1:45 PM, sergio_101 <sergio.rrd at gmail.com> wrote:
> 
> i am currently writing a facebook application in seaside. one of the most important pieces of data i need to retrieve is the user's friends list. unfortunately, this could end up being a substantial amount of data. fortunately, the load time for this data is not horrible, just a few seconds.
> i am making the assumption that while interacting with my app, the user will not be adding new friends mid stream, and that during each session, the friends list will be static.
> 
> what i would like to do is make this happen completely behind the scenes, so that when the user logs in, the request for the friends list is fired off RIGHT AFTER the page is rendered.
> i read the section on concurrency in 'deep into pharo', and while incomplete, it makes enough sense for me to try it.
> my question is.. i am going to do something like:
> 
> [currentUser updateData] fork
> 
> 1. if i want to do that RIGHT AFTER rendering, can i put that at the end of renderContentOn: html ?
> 2. when i want to work with the data, how would i know if it was done updating? i was thinking of using a semaphore.. but how would i let the next process know to keep waiting until the process was done? i would want to do something like: getFriendsList (but make sure process that populates it is done before running the request).
> 
> thanks!
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside