[OSC_dev] Adding OSC support to VLC

[salsaman at xs4all.nl]

On Tue, November 25, 2008 02:13, Pascal Baltazar wrote:
> Hi again !
>
> a few comments :
>
> Le 25 nov. 08 à 01:58, salsaman at xs4all.nl a écrit :
>
>> OMC (Open Media Control)
> IMHO, this seems a far better name for the protocol, considering that
> it doesn't address sound-related stuff only any more...
>>

Right. There seems to be a general support for this naming.


>> However, there has never seemed to be much of an interest amongst
>> other
>> developers for this, perhaps that will change as more and more
>> multimedia
>> applications start to implement OSC.
> I have the feeling that this question generated a lot of interest from
> the community, and also a lot of propositions, but it lacked any
> proper coordination....
>>

Would people be interested if I were to create a wiki on wetpaint.com ? I
am using this site for other documentation and have found it very useful:

- it`s free
- editing can be limited to group members only
- anyone can add notes to a page however
- it has a simple editing interface
- it allows embedding of images ("photos" !)
- it allows the whole tree to be dumped as html pages







>> /name - returns the namespace of the application
> - shouldn't this rather return the namespace that is just below a
> certain node, to avoid a lot of unnecessary data to be sent ?
> - shouldn't a difference be made between queries and commands ?

Yes, that is one thing we should consider.

Certainly some commands need to be common across all apps., for example,
we should standardise on something like:

/app/open_status_socket <port> [<host>]

otherwise there is no standard way to initiate a conversation with an
unknown app to get any further information.

After this, a second more general level, e.g.:

/app/get/name

or /app/name/get

/app/ping

etc.


Gabriel.
http://lives.sourceforge.net