<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] Email link and seaside workers</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>That would be load balancers work, but of course the more reliable way to do this would be to persist the state you are linking instead of using continuations, who knows if that worker will even be available 2 min from now, you can't assume that it will.<BR>
<BR>
Cheers!<BR>
<BR>
-Boris (via BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: 'Seaside - general discussion' <seaside@lists.squeakfoundation.org><BR>
Sent: Mon Jun 02 17:17:15 2008<BR>
Subject: [Seaside] Email link and seaside workers<BR>
<BR>
Hi there,<BR>
<BR>
has anybody faced a situation in which you have 4 balanced seaside<BR>
workers (sticky session and all that balancer stuff) and is able to send a<BR>
continuation secure link that will make the user to reach the right session on<BR>
the right seaside worker?<BR>
<BR>
Should be added a var beside _s and _k? like _w for the worker<BR>
dissambiguation? Who and how will disambiguate that?<BR>
<BR>
thanks,<BR>
<BR>
Sebastian Sastre<BR>
<BR>
_______________________________________________<BR>
seaside mailing list<BR>
seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>