[Dev] 'get' revisited

[jb at integralive.org]

Hi Steve:

On Fri Mar 30, Stephen Sinclair wrote:

> I do agree that it's not strictly necessary, except that I think maybe
> it's more semantically explicit to use "get".
> Personally (in some non-Integra work) I've been using /get with an
> argument to specify a timer interval at which the value should be
> auto-reported.
>

OK, I can see that this is a good reason for using a 'get' message.
Perhaps this is something that should be considered for the OSC protocol
spec...

> One thing to consider is how this might interact with the OSC-route
> object in Max.  Of course we shouldn't cater too much to specific
> implementations, but OSC-route doesn't make it so easy to differentiate
> between messages with different numbers of arguments.  The output of
> OSC-route would have to go into a "zl len" object to figure out the
> number of arguments, which would perhaps control a select object, etc..
> No nearly as clean as simply adding an argument to OSC-route.

I'm not sure what you mean here. Could you send an example?

> Also, what would happen for messages with no arguments?  These do
> exist.. events and such.  For example, a granular synth I made takes a
> message that causes it to release the sustain on its volume envelope.
> Granted, there aren't all that many examples, but it's certainly a
> possible case to consider.

I don't see this as a problem. '/foo' is just an address, so we can
specify whatever behavior we like when it receives a message with zero
arguments. /foo, when sent an empty message could cause the value of the
variable 'foo' to be sent as an output from the module, equally it could
result in the execution of some function or process.

> Just some thoughts.  By the way, did you attach your example?  I don't
> see it attached to the email.

It's attached now.

Jamie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: linfunc.tgz
Type: application/x-compressed-tar
Size: 1472 bytes
Desc: not available
Url : http://integralive.org/pipermail/dev_integralive.org/attachments/20070330/ee4a7653/attachment.bin