-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Peach wrote: > IOhannes m zmölnig wrote: > >> somewhat related is the question of system exclusive ressources (e.g. a >> port for [netreceive]). >> i find it highly frustrating that all of the network server objects will >> plainly refuse to instantiate if they cannot allocate the given port. >> i would very much appreciate, if i could get feedback on the success and >> retry another port. > > > Do you mean the object should sit there semi-instantiated until you type > in a usable port number, or just fail to instantiate but leave a message > saying why it failed?
what i would love is: - - object instantiates even if resource is already used exclusively by somebody else - - object has a method to query it's status (so user knows, that resource could not have been allocated) - - resource can be specified by user via messages (so user can chose an alternative resource) with [netreceive] this means: - - [netreceive 22] will fail to grab resource (ssh is running) but instantiates - - [status( message to netreceive gives "0" on status outlet - - [port 2222( to netreceive will (free current resource) and try to bind to port 2222 - - [status( now gives "1" mfgasr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksEPWAACgkQkX2Xpv6ydvSU3gCfYyT4UJbm98hFTXD0XAbJVLpc l0gAn0yh8se4CFKN90msuSIdo6bfCTrR =kdZL -----END PGP SIGNATURE----- _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
