[Seaside] Server Identification in Session Keys

[Philippe Marschall]

2010/8/17 Sven Van Caekenberghe <sven at beta9.be>:
> Hi,
>
> I am trying to configure Apache 2's mod_proxy_balancer with sticky sessions towards multiple Seaside 3 instances.
>
> What I need, apart from starting multiple VM's with the same image running on different ports (I am working on one machine), is that each VM adds a server identification to the session key (_s), so that the balancer can route everything in the same session to the same instance.
>
> How can this be done ?
>
> As far as I understand, it is WAApplication (WARegistry>>#handleFiltered:) that hands out session ID's in the _s parameter (#keyField), but I cannot immediately find where the session ID's are generated (is it WACache>>#store using WAKeyGenerator ?) and how I could interfere in a clean way.
>
> Has anyone done this before ?
>
> Thx for any help/pointers,

Seaside-Cluster [1] does this. You need to replace WAApplication with
WAClusteredApplication and then configure the route on the
application.

The easiest way to do this is using:

WAAdmin makeAllClusteredWith: yourRoute

 [1] http://www.squeaksource.com/ajp.html

Cheers
Philippe