Thank you Cees,<br> You would somehow use a persistent Seaside session on memcached ?<br> Is that what you suggested for sharing users' sessions?<br> Or would you force, by other means, http requests coming from the same user session to hit the same Seaside image?
<br> Does anybody know how did the guys at <a href="http://dabbledb.com">dabbledb.com</a> solve this?<br> Cluster databases can be set up easily with PostgresSQL, so I think that could be solved.<br> Thanks again.<br>
<br><br> r.<br><br><br><br><div><span class="gmail_quote">On 7/25/06, <b class="gmail_sendername">Cees De Groot</b> <<a href="mailto:cdegroot@gmail.com">cdegroot@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
With Linux and memcached, I think it would be relatively trivial to<br>set something up. The bottleneck in these cases is usually the<br>database...<br><br>On 7/25/06, Ramiro Diaz Trepat <<a href="mailto:ramirodt@gmail.com">
ramirodt@gmail.com</a>> wrote:<br>> I am pushing, smoothly but firmly, inside my company to start using<br>> Seaside. But I still have this question that I cannot answer myself.<br>> If one builds a seaside application that happens to become real
<br>> popular, is there a not so comlex way to make a Seaside cluster for<br>> load balancing, sharing user sessions, or even handle fault tolerance?<br>> If not, what would be the proper way to handle a lot of traffic?
<br>_______________________________________________<br>Seaside mailing list<br><a href="mailto:Seaside@lists.squeakfoundation.org">Seaside@lists.squeakfoundation.org</a><br><a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br></blockquote></div><br>