Barrie Treloar wrote:
tcp/ip has an easy enough state diagram to google for.
udp being connectionless doesn't seem to have such a diagram.
I don't think it ha anything to do with the underlying newtork state.
The session states I'm talking about is the application session : if you
don't manage it correctly, you are likely to get strange result,
regardless of the protocol you use (TCP or UDP).
You can always manage a session even on a connectionless protocol,
assuming that the client and the server share the state (typicaly what
it's done on Web servers with cookies or JSessionId :). But if you don't
check the session's state, you're dead ;)
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
