Friday, September 5, 2003 07:23 AM
Depends on the context. There are many different specific kinds of stateful objects with "session" in their names, in many different kinds of contexts; perhaps a generalization would be that a "session" is a name for the collection of stateful aspects, objects etc. involved, where two different things have identified each other (usually at least one way involves authentication e.g. client authenticated to server, sometimes server also authenticated to client too), and are continuing an ongoing conversation, perhaps subject to some "time out" in the case of inactivity. Usually but not always (peer to peer) there is an asymmetry involving a "client" (requestor) and "server" (requestee, service provider), and the "session" information is maintained by the "server", subject to continuing identification/authorization of the "client" (e.g. session cookies repeatedly presented by client in new requests, with Java servlet http sessions).
Try "man -k session" on a Unix box for instance.
Some specific examples (of different contexts that each have their own kind of "session") include Posix process groups, SSL, X Windows, telnet, terminal tty i/o, Java servlets, EJB's, JMS, JavaMail (IMAP), Oracle PL/SQL, ......