Joe Steeve wrote:
,----
| After an address resolution, the client is going to be connecting to
| only one IP., hence there wont be a problem. (when using DNS to point
| to different servers depending on load)
`----
Thats not my point. The application is where it matters. The first
run, The user might get a session cookie from one machine but during
the next 'click' it might go to a different front-end. In large scale
solutions data replication and clustering is a solution. In small
scale, I can only think of having custom session handling functions
that write to, say, NFS mounted directories or write to a MySQL
DB). So wondering how these guys might have set this up.
cheers,
-Suraj
--
,-----------------[http://www.symonds.net/~suraj/]---o
| Sarabha Sastrigal was a blind flautist who died in his 30s.
`------------------------------[suraj@xxxxxxxxxxx]---o