On Tue, 2 Oct 2001, Ian Holsman wrote:
> > Each session represents a logical connection to the server. Because of
> > timeouts, the server closing the pipe, or whatever, the session spans
> > connections. But a given session will only ever open one connection at a
> > given time.
>
> I'm unsure of the difference between a 'connection' and a 'session' in
> the above diagram.
> I was thinking that the 'connection' would handle the
> keep-alives/pipelines logic for a individual connection to a server.
> or in other words the 'physical' connection.
> Just wondering what stuff would be stored at the session level.
It would be stuff that survives individual connections and can be used across
several (serial) ones, wouldn't it? SSL session IDs come to mind, there will
probably be more ...
--
Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
