[Seaside] Re: Building realtime applications with Seaside
andy.burnett at knowinnovation.com
Wed Jun 18 18:11:58 UTC 2014
> > I believe (if I remember correctly), that the app (vaguely) described
> > 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.
> Correct. Implement the real time part in Zinc and let the other things
> go through to the Seaside adapter.
Thanks guys. I want to be absolutely clear about your advice - partly for
my benefit, but also for people who might search for these answers.
If we take the example of creating a real time things to do list.
1. Seaside could be appropriate for creating e.g. the login system,
account management, reporting etc. Basically, anything that doesn't need to
be updated in real time, and shared between users synchronously
2. The real time components would be handled by Zinc, and integrated
into the overall application.
If I have got that right, this poses some other questions:
1. How does one handle session management and authentication between the
two elements. For example. I login to the Seaside session on port 80, and
navigate to the real time url. Let's assume Zinc is running on port 3000.
Is there any - built-in - way for the Zinc server to know that I am
authenticated already? Or, do I have to roll my own approach?
2. What do you recommend on the client side for listening to the
changes. I know that Nico built some classes that link Amber with Pharo,
but I don't know if they help on the real time side. Sven, what have you
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside