[OSC_dev] Managing different osc implementations

[IOhannes m zmoelnig]

Jeff Glatt wrote:
[...]
> For example,
> the author of PD/Max doesn't care if some third party utility
> works with every other app that does basically what PD/Max
> does. He cares only that the 3rd party app supports PD/Max --

how does this refer to the OSC-implementations in Pd or Max?
the author of Pd/Max hasn't even started using OSC as a network protocol
yet; instead he is still using FUDI;
or are you referring to the people who have written OSC implementations
for Pd and/or Max? these implementations (at least those i i know) are
generic and don't know anything about 3rd party apps, do not impose any
limitations on OSC-paths;
are you also implying that the implementors of the TCP/IP stack on (pick
your favourite OS) did not give a shit on interoperability with other
OSs, just because you cannot transport any meaning on the transport layer?
or are you talking about authors of applications written in Pd and/or
Max? but why do you call them "author of PD/Max" then?

don't know where to put this in this mail:
OSC is not on the application layer, but slightly below it.
oscit, OMC and however they are all called are application layer
protocols, on top of OSC.


sorry. couldn't resist...


fgamdrs
IOhannes