Hello all,
Recently I worked on an implementation of the FUDI protocol in
Actionscript. The Library emulates the netreceive and netsend objects in
Flash to communicate with pd.
Since Flash is very restrictive regarding socket connections and can
only act as listener but not as server, I had to
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
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
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
Justin Glenn Smith escribió:
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
On Tue, 2010-02-23 at 21:04 +0100, Matteo Sisti Sette wrote:
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
