aboutsummaryrefslogtreecommitdiff
path: root/doc/tutorials/networking/Attic
diff options
context:
space:
mode:
authorHans-Christoph Steiner <eighthave@users.sourceforge.net>2006-05-05 07:23:54 +0000
committerHans-Christoph Steiner <eighthave@users.sourceforge.net>2006-05-05 07:23:54 +0000
commit5140196012f3adb5788b0c0533fe60ae5befdd5b (patch)
tree5693a02db07757bbc72b36d10afa7f1fd3742e32 /doc/tutorials/networking/Attic
parent9c28b4bb7d0bf90a6d0506ac7c2fd1fa13f1bca8 (diff)
first sketch on net intro
svn path=/trunk/; revision=5048
Diffstat (limited to 'doc/tutorials/networking/Attic')
-rw-r--r--doc/tutorials/networking/Attic/01.netsend_netreceive.pd36
-rw-r--r--doc/tutorials/networking/Attic/02.tcp_and_udp.pd31
2 files changed, 0 insertions, 67 deletions
diff --git a/doc/tutorials/networking/Attic/01.netsend_netreceive.pd b/doc/tutorials/networking/Attic/01.netsend_netreceive.pd
deleted file mode 100644
index 2cdb37e8..00000000
--- a/doc/tutorials/networking/Attic/01.netsend_netreceive.pd
+++ /dev/null
@@ -1,36 +0,0 @@
-#N canvas 15 58 636 456 10;
-#X obj 8 10 cnv 15 400 40 empty empty netsend_netreceive 20 12 0 24
--228992 -66577 0;
-#X obj 56 211 send \$0-local-data;
-#X obj 56 342 receive \$0-local-data;
-#X obj 60 174 hsl 150 20 0 127 0 0 empty empty empty -2 -6 0 8 -225271
--1 -1 0 1;
-#X obj 59 381 hsl 150 20 0 127 0 0 empty empty empty -2 -6 0 8 -262144
--1 -1 0 1;
-#X obj 311 174 hsl 150 20 0 127 0 0 empty empty empty -2 -6 0 8 -225280
--1 -1 0 1;
-#X obj 311 381 hsl 150 20 0 127 0 0 empty empty empty -2 -6 0 8 -262144
--1 -1 0 1;
-#X obj 308 261 netsend;
-#X obj 308 341 netreceive 34567;
-#X msg 326 222 connect localhost 34567;
-#X obj 308 280 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0
-1;
-#X obj 415 360 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0
-1;
-#X text 329 279 <-- connection status;
-#X text 433 360 <-- connection status;
-#X msg 327 241 disconnect;
-#X msg 308 199 send \$1;
-#X text 45 78 At the most basic level \, networking in Pd works a lot
-like the standard [send] and [receive] objects \, except there is a
-network port number rather than a send/receive name:;
-#X connect 2 0 4 0;
-#X connect 3 0 1 0;
-#X connect 5 0 15 0;
-#X connect 7 0 10 0;
-#X connect 8 0 6 0;
-#X connect 8 1 11 0;
-#X connect 9 0 7 0;
-#X connect 14 0 7 0;
-#X connect 15 0 7 0;
diff --git a/doc/tutorials/networking/Attic/02.tcp_and_udp.pd b/doc/tutorials/networking/Attic/02.tcp_and_udp.pd
deleted file mode 100644
index 514cf849..00000000
--- a/doc/tutorials/networking/Attic/02.tcp_and_udp.pd
+++ /dev/null
@@ -1,31 +0,0 @@
-#N canvas 185 93 644 464 10;
-#X obj 511 62 import maxlib;
-#X obj 10 10 cnv 15 400 40 empty empty tcp_and_udp 20 12 0 24 -228992
--66577 0;
-#X text 11 66 There are two main protocols for transmitting data over
-networks: TCP and UDP.;
-#X text 35 119 TCP is the most common \, it stands for Transmission
-Control Protocol. Basically \, that means that the protocol manages
-the transmission of the data. With TCP \, when you send a packet of
-data \, its guaranteed to arrive.;
-#X text 34 202 By default \, most networking objects in Pd use TCP:
-;
-#X obj 54 223 netsend;
-#X obj 266 224 netclient;
-#X obj 359 224 netserver;
-#X text 178 295 UDP stands for User Datagram Protocol. It is a lightweight
-\, simple protocol that is meant to be as quick and small as possible.
-The downside is that the data packets are not guaranteed to arrive.
-;
-#X obj 35 180 pddp/pddplink http://en.wikipedia.org/wiki/Transmission_Control_Protocol
-;
-#X obj 177 355 pddp/pddplink http://en.wikipedia.org/wiki/User_Datagram_Protocol
-;
-#X obj 132 224 netreceive 32194;
-#X obj 265 386 netreceive 32194 1;
-#X obj 187 386 netsend 1;
-#X obj 407 386 sendOSC;
-#X obj 478 386 dumpOSC 32192;
-#X text 180 409 One advantage to UDP is that you do not need to maintain
-a connection to receive data. Whenever you open a UDP port \, you will
-start receiving data.;