[Seaside] Re: Building realtime applications with Seaside

[Sven Van Caekenberghe]

I believe (if I remember correctly), that the app (vaguely) described here

  http://forum.world.st/Another-Pharo-based-solution-released-td4762341.html

is also using web sockets. But you should ask.

It is perfectly possible to combine Seaside with other servers/services in the same or different images. But this is a broad subject.

On 18 Jun 2014, at 11:15, Philippe Marschall <philippe.marschall at gmail.com> wrote:

> On Wed, Jun 18, 2014 at 12:28 AM, Andy Burnett
> <andy.burnett at knowinnovation.com> wrote:
>> 
>> <<
>> 
>> Hi Andy,
>> 
>> There is also Zinc-Server-Sent-Events:
>> 
>>  http://forum.world.st/Zinc-Server-Sent-Events-td4705635.html
>> 
>> Nothing spectacular, but it should work.
>> 
>> Sven
>> 
>>>> 
>> 
>> Hi Sven,
>> 
>> I hadn't spotted that you had added SSE. That's great!
>> 
>> So, I think my new question is how I would wire that into a Seaside application. Is there a single  listener class that can announce data changes. Or would each component somehow wire its model to the connection?
>> 
>> My experience with Seaside is very limited, so if there is a good example/guide to this specific question, i.e. handling changes to the underlying model, please nudge me in that direction.
> 
> You would separate the realtime part from the normal Seaside part.
> "realtime" doesn't currently fit well into the Seaside
> request-response model and even less so in the component and session
> model. I.e there is a lock on each sessions to prevent multiple
> requests from concurrently modifying the same component.
> 
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside