Gerry, RedBack uses a request/response model.
Each RedBack request(e.g. setting or getting a property or actioning a method on a RedBack object) is considered to be a single atomic action and is picked up by the first available RedBack responder. There is no concept of a user or session in the way of a UNIX login user or session, and subsequent requests from the same 'user' may be handled by different responders. All of which provides for scalability through connection pooling, but also requires that any authentication has to be handled at the application level. Brian ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
