summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAndreas Baumann <abaumann@yahoo.com>2009-04-02 17:55:09 +0200
committerAndreas Baumann <abaumann@yahoo.com>2009-04-02 17:55:09 +0200
commitbeaacec9990b0261b656a93d97d98bb17cba623d (patch)
tree68339e23b0e4bce7d88b60752734925e7701d3d9 /docs
parentdbd53b4ec7ce2553ad2cf1518d1e2462fac7f0bc (diff)
downloadwolfbones-beaacec9990b0261b656a93d97d98bb17cba623d.tar.gz
wolfbones-beaacec9990b0261b656a93d97d98bb17cba623d.tar.bz2
more networking docu
Diffstat (limited to 'docs')
-rw-r--r--docs/network/README18
1 files changed, 17 insertions, 1 deletions
diff --git a/docs/network/README b/docs/network/README
index c817332..edfacb2 100644
--- a/docs/network/README
+++ b/docs/network/README
@@ -1,5 +1,19 @@
Goals:
--
+- text-based protocols, telnetish, TCP/IPish
+- comminucate over sockets (requests to services), both in client-
+ (connect) and server-mode (bind,listen,accept)
+- there should be no difference whether we talk to sockets, pipes
+ of an external process or a file
+- how events are colleted (select,poll,kqueue,/dev/poll,epoll,etc.)
+ should be abstracted
+- should be usable in single- and multithreaded environment
+- we should scale, but not in the webserver-style (which would be
+ optimization done too early in the wrong direction!)
+- protocols should be designable like a Russian Nested Doll for being
+ fast in business layer to device new protocols suiting the problem
+- reach the 100MBit/s sustained transfer rate (yes I know, there are
+ Gigabits/s NICs out there, but their speed is almost impossible to
+ reach)
Links:
- Boost ASIO: on design
@@ -10,4 +24,6 @@ Links:
machine, a lot of useful links
- http://www.bullopensource.org/posix: POSIX effort to normalize
asynchronous I/O interfaces
+- Boinc: http://boinc.berkeley.edu: some ideas around protocol FSMs in
+ networking