haug%vax.runit.unit.uninett@TOR.NTA.NO (Steinar Haug) (06/30/88)
Hi, I wonder if anybody could explain to me the practical differences between DECnet 'network name' and 'object number'. Using $QIO with the ACPCONTROL function I can assign either a name or a number to my task, but I cannot seem to find any information in the 'Guide to Networking on VAX/VMS' about why I should choose one over the other. (I'm wondering about this because I'm making a server which accepts multiple inbound connections. I have already received examples of client/server code from the net. Thanks to all who responded!) Steinar Haug ! ARPA: haug%vax.runit.unit.uninett@tor.nta.no Database Research Group ! or: steinar@tor.nta.no Computing Research Center! EAN(X.400): haug@vax.runit.unit.uninett University of Trondheim ! BITNET/EARN: haug@norunit 7034 Trondheim, NORWAY ! VMS Mail: psi%02422530001003::12423
LEICHTER@VENUS.YCC.YALE.EDU ("Jerry Leichter ", LEICHTER-JERRY@CS.YALE.EDU) (07/04/88)
I wonder if anybody could explain to me the practical differences between DECnet 'network name' and 'object number'. Using $QIO with the ACPCONTROL function I can assign either a name or a number to my task, but I cannot seem to find any information in the 'Guide to Networking on VAX/VMS' about why I should choose one over the other. (I'm wondering about this because I'm making a server which accepts multiple inbound connections....) Object numbers are intended for a small set of "well-known", standardized network objects. The set HAS to be small, since an object number is just a single byte! I suppose very simple-minded DECnet implementations might understand a couple of the standard numbers but not have the smarts to interpret an object name. Can't say I've ever heard of such an implementation, but it's possible.... I'd use an object name. -- Jerry