|Forwinder||Aug 22, 2008 8:11 am|
|Frank Barknecht||Aug 22, 2008 9:30 am|
|IOhannes m zmoelnig||Aug 23, 2008 3:07 am|
|Luke Iannini||Aug 23, 2008 4:15 am|
|IOhannes m zmoelnig||Aug 23, 2008 5:02 am|
|Claude Heiland-Allen||Aug 23, 2008 5:14 am|
|Frank Barknecht||Aug 23, 2008 5:18 am|
|Claude Heiland-Allen||Aug 23, 2008 5:25 am||.c|
|Martin Peach||Aug 23, 2008 7:55 am|
|Frank Barknecht||Aug 23, 2008 8:00 am|
|Stephen Sinclair||Aug 23, 2008 9:33 am|
|forwind||Aug 25, 2008 10:33 am|
|Hans-Christoph Steiner||Aug 26, 2008 4:58 pm|
|Subject:||Re: [PD-dev] dump OSC bugs?|
|From:||Hans-Christoph Steiner (ha...@eds.org)|
|Date:||Aug 26, 2008 4:58:55 pm|
On Aug 23, 2008, at 10:55 AM, Martin Peach wrote:
Frank Barknecht wrote:
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
whenever i find the time, i want to add a note into the constructor of the OSCx objects, so you get a warning each and everytime you create one of these objects.
I think, such warnings may be a bit too patronizing. Also OSCroute doesn't have any critical bugs AFAIK.
Bundling some replacement abstractions build with Martin's osc objects for ease of transition would be useful, though, and the osc help files could benefit from some polishing like replacing [prepend] with a no-nameclash solution based on [list] etc.
Probably moving the mrpeach osc objects (routeOSC, packOSC and unpackOSC) into an /osc folder and the net objects (udpreceive, udpsend, tcpreceive, tcpsend, tcpclient, tcpserver) into a /net folder would be a good idea, making them easier to find for the uninitiated. Unfortunately it would break some existing patches that currently use the /mrpeach prefix. And I'm not sure how much svn enjoys moving things around like that.
Just leave the objects in 'mrpeach' and old patches won't break. Then the 'mrpeach' lib could be deprecated in stages.
I think having clean, well organized 'net' and 'osc' libraries would be great. Before just moving them to 'net' and 'osc', I think there should be a clear idea of what a full-fledged 'net' and osc' libraries would look like. Each library should have standard interfaces and messages for the objects in that library.
'osc' would probably be an easier place to start, since it will most likely be smaller.
Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism. - retired U.S. Army general, William Odom