On Sat, Mar 26, 2005 at 12:43:45PM +0000, Martin Habets wrote: > Hi Steve, > > Was testing this scenario today, which may look familiar to you: > > - I created a server with some methods: '/ping/documentation' and > '/osc-schema/documentation', both of which use the same handler 'doc'. > - I send query '/*/documentation' to the server. > - 'doc' got called twice with path '/*/documentation'. > > The unexpanded path makes it impossible for the handler to determine > what container was intended. In my interpretation the OSC spec is not > completely explicit on this point, but I think the intention was to > send the expanded path to the handler. The spec is specific in stating > that '*' is invalid in an OSC method, and it talks about the "OSC Address > of a OSC Method".
That sounds good, its just an oversight on my part, the patch makes perfect sense to me. I'l apply it when I get the chance FWIW, I'm planning to add API support for the documentation etc. features at some point, I do the sub-path listing stuff allready. But, I'l make sure I dont stomp on anything done explicitly by developers. - Steve
