On May 1, 2006, at 6:35 PM, Martin Peach wrote:
Hans-Christoph Steiner wrote:
I have to say that I really think that tcp and udp objects should
be bidirectional. TCP and UDP sockets are, so the objects
should represent that. I've done quite a bit of network
programming with Pd and I never use [netsend]/[netreceive]. I
always use [netserver]/ [netclient] because of the bidirectional
connection and the client management of the [netserver].OK, it looks like basically the same modifications are needed to
change [netserver] and [netclient] to byte mode from pd message
mode as I did with [netsend] and [netreceive]. Will have a go.
Just out of curiousity, why do you use byte mode rather than message
mode? Do you mean that you are sending one byte per packet?
What about just a [socket] object which could also do UNIX sockets,
or any other kind? It would probably be more work, but worth it in
the long run. Then [tcpsocket], etc. could be a Pd object.
.hc
Martin
I think the "server" aspect could be a separate object. I think
the socket objects should represent just the sockets, and how the
sockets work. .hc _____________________________________________________________________ ___ ____ "Information wants to be free." -Stewart Brand _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
"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