123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300 |
- -241291 -1;
- -241291 -1;
- -258699 0 1;
- 0;
- of a packet oriented protocol correctly \, unlike [tcpserver] \, which
- might mix up packets from different sockets.;
- abstraction \, which should be named [tcpsocket.PROTOCOL]. currently
- available are the protocols:;
- to do so:;
- out of the incoming stream for the desired protocol. don't forget to
- implement a reset mechanism \, in case a socket is closed in the middle
- of packet transmission.;
- replacement for [tcpserver]. it uses same the same inlet and outlet
- configuration as [tcpserver].;
- -66577 0;
- 1;
- -66577 0;
- 1;
- -66577 0;
- ' \; ';
- FUDI-compliant messages. this should be done by the user.;
- a message with client_1 and see \, how the server behaves.;
- -66577 0;
- 1;
- -66577 0;
- 1;
- -66577 0;
- -1 0;
- 1) and 2);
- suitable for tcp transport.;
- [tcpsocket.OSC] already unwraps the OSC message;
- ;
- instance of a socket handler abstraction [tcpsocket.PROTOCOL] for each
- opened socket. every socket handler creates proper packets from the
- incoming stream and sends them to the left outlet of [tcpsocketserver].
- ;
|