On Fri, 12 May 2006, Martin Peach wrote:
I should be able to merge these into a single [tcp] that accepts connections as well as initiating them.
If you make this then I want it to be part of the *internals* of PureData-devel.
It seems not useful to do the same for udp because udp is not a connection-oriented protocol -- you can send messages back and forth on separate sockets without any problem using [udpsend] and [udpreceive], so probably [udp] would be a combination of [udpsend] and [udpreceive].
I prefer to have both halves of the protocol in the same object-class. This is for symmetry with other protocols (in this case, with [tcp]). Making it like this doesn't really add to udp support itself but it doesn't remove any feature either, has little overhead, and increases the uniformity across similar object-classes.
What would be the name of a unix-socket version? [unix] seems too vague.
[pipe] is already taken. [namedpipe] and [localsocket] could be fine.
However, putting "socket" in the name is contrary to the naming of [tcp]
and [udp]. OTOH, I don't care much for making those names three letters
long, because they aren't used often enough. (it's not like [t] or [f])
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada