-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [email protected] wrote: >> Personally, I think it should instantiate, and throw a pd_error() >> saying that it can't function without a port number. Another option >> for netreceive is to pick a default port number. >>
this is not something i care about. people wanting to use the network, should at least understand they need a port :-) i am really talking about tyring to listen to a certain port which is already used by somebody else. the object will just fail to create in this case (though it won't fail to create in other circumstances, e.g. when no other app is listening to this port) an other case: a dummy user sits behind a firewall which has port 8888 open, but unfortunately the patch uses port 7777. the dummy user has to either phone the network admin to open up port 7777, or find their way through the patch and change the [netreceive]. > So maybe Pd needs a default port number that could be inscribed in > /etc/services and /etc/inetd.conf, or at least m_pd.h. i think this will make my problem (multiple servers listening on a single port) even worse! imagine all those innocent [netreceive]s (with no args) sitting around. furthermore, a default port is useful, if two applications using this port can talk to each other without knowing more. ports are usually reserved for protocols rather than applications (port 80 is http, not apache; FUDI is not really a protocol in this sense) fg asdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksEQmwACgkQkX2Xpv6ydvQKJACfaU1/tqVCGiIRPj/Lp7sv05Tp OM4AoLuyIYlXl+2gA7a8Ewb3svdJvLo+ =Vq40 -----END PGP SIGNATURE----- _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
