On Mon, 2005-04-04 at 17:02 +0100, Martin Habets wrote: > On Thu, Mar 31, 2005 at 03:07:28PM +0100, Steve Harris wrote: > > > Am working on a library for this stuff + service discovery on top of > > > liblo. Sub-path listing is the only thing I haven't coded up yet. Still > > > a good deal of testing to do. > > > > You might want to get in touch with Dave robillard (sp?) as he's working > > on something similar. > > Yes, we had a nice discussion a while back. Here's a recap of his scenario: > > On Tue, Mar 01, 2005 at 01:27:38PM -0500, Dave Robillard wrote: > > Implementation wise, the scheme goes something like this: > > > > - client broadcasts it's existance via rendezvous > > - patching server replies to client, so now both are aware of each > > other's existance > > - (any) client can now set destinations for client. in other words, > > osc-patch-bay functionality now works > > > > When a destination is added/removed, the patching server will notify the > > client (via OSC), and the client will update it's list of destinations > > appropriately (this will all be abstracted by liblo's API though). > > Dave, do have any more details on this? i.e. the suggested OSC addresses to > add/remove a destination.
Well, I've talked a bit more with Steve about this, and have separated this 'patch bay' stuff from actual service discovery conceptually (though one depends on the other of course). Basically we just need a lo_discover(client_id_string) method that allows figuring out what clients are out there (optionally, with the given name). I started to implement this but it got pushed down the priority list to make room for some more important/urgent things.. > > > Am working on a library for this stuff + service discovery on top > > > of liblo. Hmm. Not sure I like the sound of that. Service discovery belongs inside liblo itself, IMO. -DR-
