thanks for that, 

in fact, some of my clients need the same infos and this is why I first try to do multicasting
but reaching multiple clients on the same host is different than addressing one packet to different hosts...

for now all my clients try to connect around each 10 second to server to query some infos and to update their state
but I could guarantee that only one client will try to connect at a time
so it could be difficult to use a server which doesn't accept more than one connection...

or maybe i'm wrong and there is another solution, not based on networking ?



--
do it yourself                      
http://antoine.villeret.free.fr


2013/7/3 IOhannes m zmoelnig <zmoelnig@iem.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-07-03 12:37, Antoine Villeret wrote:
> that's why I switched to [udpserver].

i guess you meant [tcpserver] instead of [udpserver].

in any case, i'm thinking about removing the multi-client feature of
iemnet's [udpserver], so you could only send replies to the *last*
client that connected.

the idea is, that you could use it as a server that can be queried by
clients (in a ping/pong sort of ways: the clients sends a query packet
and is immediately answered with an answer packet), similarily to DNS.

maintaining a number of connections is simply impossible with a
connectionless protocol.

fgamsdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlHUMTUACgkQkX2Xpv6ydvQMpQCeOx09OJYP3LszFo39rqGjjYoL
l5gAoN5Y6sdSXR06w4hBSw2+WZKGS6HH
=WJYl
-----END PGP SIGNATURE-----

_______________________________________________
Pd-dev mailing list
Pd-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev