aboutsummaryrefslogtreecommitdiff
path: root/README.txt
diff options
context:
space:
mode:
authorIOhannes m zmölnig <zmoelnig@users.sourceforge.net>2010-03-26 14:35:41 +0000
committerIOhannes m zmölnig <zmoelnig@users.sourceforge.net>2010-03-26 14:35:41 +0000
commit220e3caa32594e32878bc57e5932b49f327609f9 (patch)
tree8dc04403a34a0466e016e6983832d46ab775b953 /README.txt
parent5db5e5914161c1b45fe70052decff23970a732ba (diff)
more mission and scratchpad
svn path=/trunk/externals/iem/iemnet/; revision=13287
Diffstat (limited to 'README.txt')
-rw-r--r--README.txt10
1 files changed, 9 insertions, 1 deletions
diff --git a/README.txt b/README.txt
index 94fd106..4c18979 100644
--- a/README.txt
+++ b/README.txt
@@ -43,7 +43,15 @@ the lib doesn't know anything about the actual transport protocol. it only
interacts with a socket.
easy to run:
-think speed
+think speed, think reliability
+all known implementations for pd are either slow or will freeze Pd when under
+_heavy_ load. most do both.
+iemnet wants to provide objects whih allow you to saturate the network
+connection and still keep Pd reactive.
+(sidenote: saturating even a 100MBit network with Pd might lead to audio
+dropouts; this is not necessarily related to the network but rather to the
+amount of data processed by Pd...)
+