<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><<<<br>
On Wed, Jun 18, 2014 at 8:11 PM, Andy Burnett<br>
<<a href="mailto:andy.burnett@knowinnovation.com">andy.burnett@knowinnovation.com</a>> wrote:<br>
><br>
> ᐧ<br>
> <<<br>
>><br>
>> > I believe (if I remember correctly), that the app (vaguely) described here<br>
>> ><br>
>> > <a href="http://forum.world.st/Another-Pharo-based-solution-released-td4762341.html" target="_blank">http://forum.world.st/Another-Pharo-based-solution-released-td4762341.html</a><br>
>> ><br>
>> > is also using web sockets. But you should ask.<br>
>> ><br>
>> > It is perfectly possible to combine Seaside with other servers/services in the same or different images. But this is a broad subject.<br>
>><br>
>> Correct. Implement the real time part in Zinc and let the other things<br>
>> go through to the Seaside adapter.<br>
>><br>
>> Cheers<br>
>> Philippe<br>
>><br>
> >><br>
><br>
> 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.<br>
><br>
> If we take the example of creating a real time things to do list.<br>
><br>
> 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<br>
> The real time components would be handled by Zinc, and integrated into the overall application.<br>
<br>
Correct.<br>
<br>
> If I have got that right, this poses some other questions:<br>
><br>
> 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?<br>
<br>
I would run both on the same port. Remember Seaside is not a web<br>
server, Zinc is. Zinc does it's thing first and the delegates to<br>
Seaside. For the real time parts you would simply implement them in<br>
Zinc an then not delegate to seaside.<br>
I would try to avoid dependencies on seaside sessions from the<br>
realtime part. Instead I would depend only on domain objects. You may<br>
need a "message bus" between the parts.<br>
<br>
Cheers<br>
Philippe<br>
>>><br>
<br></blockquote><div><br></div><div>Thanks everyone.</div><div><br></div><div>Philippe, I hadn't quite understood the relationship between Zinc and Seaside, so that is a useful observation. I might try splitting things the way you suggest.</div>
<div><br></div><div>Cheers</div><div>Andy </div></div></div></div>