|
On Mon, 21 Jun 1999, Lars Marowsky-Bree wrote:
> On 1999-06-21T13:34:10,
> Joseph Mack <mack@xxxxxxxxxxx> said:
>
> > easiest if the machine is only putting out one service (eg http)
>
> Actually, thats quite irrelevant. The load of the machine is the same
> regardless of how many services it is running. You can just use that for all
> the services, since the load will just increase faster and that will in turn
> lead to the scheduler reducing the new connections...
I was thinking along the lines that if the machine was only serving http
then you could have a program on the server looking at the
http log (or some equivalent)
>
> > :-)
> > do they come from the same port?
>
> No. SSL connections will not come from the same port, since the clients open
> many of them at once, just like with normal http.
so would we be able to differentiate all the people coming from aol by
the port number?
> > > Now, SSL carries a "session id" which identifies all requests from a
> > > browser. This can be used to separate the multiple SSL sessions, even if
> > > comeing in from one big proxy and load balance them.
> > OK
>
> But like I said: really hard to get working, and even harder to get right ;-)
I don't have a clue how it would work right now, but in
principle it is just another protocol specific handler like the ftp
handler. One of us would have to figure out the ssl protocol.
> Since this would require the connection to be established basically to the
> load balancer, which would analyse the request and then pass it on
> transparently.
yes
Joe
--
Joseph Mack mack@xxxxxxxxxxx
|
