Hi, This is a substantial change, so I'd like to give it more visibility.
It was proposed to remove support from binding more than one resource per session. Having mutliple resources per session is a corner use case. Probably nobody is using it and even fewer understand how it could possibly work. However, if you are, or otherwise need this feature, please speak up. Otherwise I'm +1 to remove it from Vysper and only allow one resource per session. Note: This of course will not change the ability to have more than one session, each with unique "full JIDs". Bernd On 28.09.11 00:44, Peter Saint-Andre wrote: > On 9/27/11 4:42 PM, Mike Mahoney wrote: >> >>> >>>> We'd be happy to >>>>> provide the patch. >>> >>> I'd be very interested to review the patch. Please open a new JIRA >>> (you can link it to VYSPER-11 if you want). >>> >>> I never implemented this because I wanted to route around >>> potential problems like having to check the well-formed-ness of >>> the client-proposed resource name and the potential runtime >>> conditions when duplicate names are bound quasi-simultaneously. >> >> I do have one question about the current resource binding. It looks >> like there is some support in there for binding multiple resources to >> a single session (such as ResourceRegistry.unbindResource()). This >> used to be specified in XEP-0193, but that is deprecated. Is there >> any objection to removing that support? > > Yeah, that was a bit of an experimental feature that never made the cut > in the XMPP world. I'd be in favor of removing it, unless folks have a > compelling use case. > > Peter >
