From 8dbec761cf858ea65900c8a094599857208d8c3a Mon Sep 17 00:00:00 2001 From: "N.N." Date: Tue, 5 Jan 2010 22:49:36 +0000 Subject: svn path=/trunk/; revision=12907 --- desiredata/man/pdsend.1 | 26 -------------------------- 1 file changed, 26 deletions(-) delete mode 100644 desiredata/man/pdsend.1 (limited to 'desiredata/man/pdsend.1') diff --git a/desiredata/man/pdsend.1 b/desiredata/man/pdsend.1 deleted file mode 100644 index 5491c745..00000000 --- a/desiredata/man/pdsend.1 +++ /dev/null @@ -1,26 +0,0 @@ -.TH pdsend 1 "1996 Mar 20" GNU -.SH NAME -pdsend \- send messages to pd on this or a remote machine -.SH SYNOPSIS -.B pdsend -\fIport-number\fR [\fIhostname\fR] [udp|tcp] -.SH DESCRIPTION -Pdsend sends messages to pd(1), via a socket conection, from pdsend's -standard input. This input can be any stream of Pd messages separated by -semicolons. This is probably the easiest way to control pd from another -application. The protocol used is easy to implement and is called FUDI. -.PP -The \fIport number\fR should agree with the port number of a "netreceive" object -within pd. The \fIhostname\fR is "localhost" by default and can be a domain -name or an IP address. The protocol is "tcp" by default; this does a handshake -to -guarantee that all messages arrive complete and in their correct order; if you -are sending messages locally or point-to-point you can often get away with -the faster udp protocol instead. -.PP -You can also use this to talk to a Max "pdnetreceive" object or even just a -"pdreceive" in another shell. If you're writing another program you're welcome -to just grab the sources for pdsend/pdreceive and adapt them to your own ends; -they're part of the Pd distribution. -.SH SEE ALSO -pd(1), pdreceive(1) -- cgit v1.2.1