On 27.09.11 21:20, Peter Saint-Andre wrote: > On 9/27/11 1:18 PM, Mike Mahoney wrote: >> Hello Everyone, > > Hi. Full disclosure: I don't work on Vysper, I just listen in on the list. > >> We're in the process of embedding Vysper into our product, which is >> going well. One of our requirements is for Vysper to accept the >> suggested resource name provided by a client. I have already made >> the necessary modifications to ResourceRegistry, >> DefaultResourceRegistry, and the classes that use them. Is this >> something the Vysper team would be interested in?
Sure. > 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. > > That would improve compliance with RFC 6120, so I say +1. :) In general, I'm +1 on this, too. However, with respect to compliance - RFC 6120 reads: "The server SHOULD accept the client-submitted resourcepart. ... Alternatively, in accordance with local service policies the server MAY refuse the client-submitted resourcepart and override it with a resourcepart that the server generates." So, are you saying that the server is required to accept resourceparts in general and only may refuse those that are not-so-well-formed? Until now, I interpreted this as that the server is still fully compliant even if it generates the resource all the time. Bernd
