On 11/24/05, Norman Rasmussen <[EMAIL PROTECTED]> wrote: > I think you can by forcing binding to an existing resource, but I'm > not sure it allows you to force an old resource off and bind a new > one.
Wont work since even binding to an existing resource would mean that I'm adding one more connected resource (albeit of a same name). What I'm asking is - shouldn't this be treated in the same way we treat server provisioning for allowing/disallowing two resources of the same name to be available? > On 11/24/05, Vinod Panicker <[EMAIL PROTECTED]> wrote: > > According to RFC 3920 - > > > > o The client is not allowed to bind a resource to the stream (e.g., > > because the node or user has reached a limit on the number of > > connected resources allowed). > > > > Wont it make sense if there is some provision to automatically logoff > > the user from a previous resource (based on server provisioning) if > > he's trying to login from a new resource? Regards, Vinod.
