Hi,
sounds like things are going well - excellent.
On Tue, 15 Jan 2002 22:41, Paul Hammant wrote:
> *Session*
>
> It now also enshrines a session id. The session id is a long. It is an
> int serial number shifted left 16 bits with a random int added (to
> prevent spoofing).
I wonder if this is needed. Some transports (ie SSL and TCP) already indicate
a session because you have constant comms and the session is broken when the
transport is teared down. It would be nice not to require the API to have a
session id associated with it but instead have the session id a
characteristeric of the transport.
--
Cheers,
Pete
"The fact that a believer is happier than a skeptic is no more to the
point than the fact that a drunken man is happier than a sober one.
The happiness of credulity is a cheap and dangerous quality."
-- George Bernard Shaw
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
