- QA'ed tutorial patches to make sure that the objects all load, and that the

  patches are all the same size and location


svn path=/trunk/; revision=10034

1 files changed, 0 insertions, 31 deletions

diff --git a/doc/tutorials/networking/02.tcp_and_udp.pd b/doc/tutorials/networking/02.tcp_and_udp.pd
deleted file mode 100644
index 514cf849..00000000
--- a/doc/tutorials/networking/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.;