|
From: Stephen S. <rad...@gm...> - 2008-02-24 18:49:19
|
On Sun, Feb 24, 2008 at 1:47 PM, Stephen Sinclair <rad...@gm...> wrote:
> On Sun, Feb 24, 2008 at 11:54 AM, Stephen Sinclair <rad...@gm...> wrote:
> > It seems that cases 1, 4, and 5 are in error. Likely to do with the
> > {} curly bracket processing, since which handler is called is
> > obviously related to the order in which they appear.
> > Another case I noticed, with handlers for /foo/bar and /foo/bing, is
> > that sending "/*" triggers both handlers, when I believe perhaps it
> > should not trigger either. I may be wrong but it's my understanding
> > that wildcards should only match up to a '/' character.
Sorry, didn't mean to imply that my patch fixes the /* problem. It
only fixes the {foo,bar} problem.
According to http://opensoundcontrol.org/spec-1_0
1. The OSC Address and the OSC Address Pattern contain the same
number of parts; and
2. Each part of the OSC Address Pattern matches the corresponding
part of the OSC Address.
So the /* problem should probably be addressed.
Steve
|