Justin Glenn Smith wrote:
Matteo Sisti Sette wrote:
This reminds me of the funny limitation that in PD a client can only send ([netsend]) and a server can only receive ([netreceive]).
Wouldn't it be great to have a [netclient] object, almost identical to [netsend] but capable of receiving as well as sending messages (an outlet for received messages just like netreceive), and a [netserver], almost identical to [netreceive] but capable of sending as well as receiving messages (an inlet with methods identical to those of netsend)?
Maybe there's already something like this in Extended, but wouldn't it deserve being included in Vanilla?
sockets are one way, you can do the same thing every other app does, and open two streams in each side: one sending, the other receiving. This can be done with the existing objects.
refer here for more info http://beej.us/guide/bgnet/
never mind, I was confused there, a normal socket does allow both send and receive.
For PD to have two-way sockets, and have them be really useful, we would have to have dynamically created connections, and this kind of thing is a little trickier in PD than it is in a textual programming language.