[Web-SIG] and now for something completely different!

[Ian Bicking]

Rene Dudfield wrote:
> Some more requirements for sessions can be found at the php page on sessions.
> 
> Hash function declaring:
>    Chosing eg md5/sha.  Also by using a distributed hash function you
> can easily route the request to a specific web server.  So with one
> rewrite rule you can have your scalable sessions/session affinity. 
> The function could simply append the number 1-100 in front of session
> id which relates to a particular webserver.

Right-o, I've seen that feature before.  Maybe create_session_id() 
should grow a prefix argument, and for now it'll be up to the glue code 
to provide that.  It's really a configuration parameter.  Though I 
suppose you could turn the SERVER_ADDR into a 8-byte code, which would 
probably identify the proper server.  Or maybe you should pick it up 
from an environmental variable... bah, it'll only be clear in the 
context of a specific environment and configuration.

> tag rewriting.  
>     ie.Which tags to do rewriting in.  eg where it appends
> ?SESSIONID=ABCFED938743523 to your output html.

That would certainly be well implemented by middleware.

> url_rewriter.tags  string
> 
>     url_rewriter.tags specifies which HTML tags are rewritten to
> include session id if transparent sid support is enabled. Defaults to
> a=href,area=href,frame=src,input=src,form=fakeentry,fieldset=

Huh, what are fakeentry and fieldset?


-- 
Ian Bicking  /  ianb at colorstudy.com  /  http://blog.ianbicking.org