> > o The provided resource identifier is already in use but the server > > does not allow binding of multiple connected resources with the > > same identifier. > > I can't remember why we even thought about allowing a client to bind > multiple resources with the same identifier, since it would play havoc > with delivery logic. Sounds to me like a clean-up item for rfc3920bis.
Depends how you read that paragraph. If you interpret 'allow binding of multiple connected resources with the same identifier' as 'allow a client to request identical resource names', then it should be ok as long as the server generates another resource name for conflicting requests (like the Google Talk server does). But if that's the case, that paragraph might be clarified that connected entities may not have the same resource. cheers, Remko
