|
On Fri, 25 Jun 1999, Lars Marowsky-Bree wrote:
> It is just that we can use the SSL session ID to do better than that and
> separate the requests all comeing in from the same proxy into multiple
> sessions and schedule them to different machines, so not all of aol.com hits
> a single https server.
is the session ID encrypted or is it in the header where we can get at it?
> Mind you I have no idea how to implement this, since this would require the
> load balancer to do scheduling based on in-band data, which we currently don't
> do at all, do we?
with NAT the packet is looked at and rewritten, that's close enough
Joe
--
Joseph Mack mack@xxxxxxxxxxx
|
