Scaling seaside: Added parameter for squeak instance

Hi,

I had a post before asking about how to encode a port
number (of the squeak instance running a web service)
into a cookie name. Phillip was right by pointing
out that the cookie name is not the obvious choice while
users can switch off cookies and seaside is able to switch
to url session handling.

The example Phillip mentioned used a port=[port number]
parameter in the url. But I don't like to expose more
information about the deployment to the outside. And I
like to have the host also identified.

I added a configuration option to WASessionConfiguration
to switch on/off use of the new parameter. I named it
instance parameter as I think off squeak instances running
on a host/port.

I added an additional method to WAApplication to generate
a parameter. I tried to mimick the seaside appearance as
much as possible. I used to parameter key _i and encoded
the host/port setting into a base64 string.

I think this could be interesting for people who care
about scaling seaside through haproxy or the like.

A changeset is attached.

regards,

Norbert

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Just as an example. My URLs look like this now:

http://127.0.0.1/seaside/webapp?_i=MjA5NzM0MDgw&_k=TBXMSgmy&_s=nAwqjrxuIBlnBvnL

thats:

_i For squeak instance
_s Session inside squeak instance
_k execution pointer since start of session

regards,

Norbert

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2007/4/19, Norbert Hartl <[hidden email]>:
You do that anyway. Clients can display and modify cookies freely.

Philippe
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Just as an example. My URLs look like this now:
>
> http://127.0.0.1/seaside/webapp?_i=MjA5NzM0MDgw&_k=TBXMSgmy&_s
=nAwqjrxuIBlnBvnL
How exactly would that add anything?  The session key is already unique to
that instance of squeak, of what benefit is the new parameter?  HAProxy is
also perfectly capable of setting and managing its own cookie for
remembering instances.

Ramon Leon
http://onsmalltalk.com

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

On Thu, 2007-04-19 at 08:41 -0700, Ramon Leon wrote: Oh, didn't know that haproxy handles its own cookies. So
the answer is easy. It adds nothing valuable :)

thanks,

Norbert

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside