Article View: comp.sys.next.programmer
Article #1598Distributed Objects and Network Name Server
From: Robert_La_Ferla
Date: Fri, 13 Nov 1992 12:24
Date: Fri, 13 Nov 1992 12:24
30 lines
1696 bytes
1696 bytes
Keywords: NeXTSTEP 3.0, Distributed Objects, Network Name Server, nmserver Reply-To: Robert_La_Ferla@hot.com Distribution: world Is there a command line utility or any utility for that matter that displays any and all registered port names in the Network Name Server? In lieu of such a utility, does enabling debugging on nmserver via -c -t -p 0 work and does it provide this information? It didn't work for me. If you register an object with a name using registerRoot:withName:, when does it cease existing in the NetNameServer? Is it removed from the server automatically when the application or task exits? Do you need to explicitly unregister the object? How? Do you use free or removeObject:? What do the following error messages mean? Unknown error code 11013 in NXReportError Unknown error code 11004 in NXReportError Inquiring minds want to know! Robert La Ferla PS. NeXT Developer Support: WE NEED MINI-EXAMPLES for Distributed Objects (especially ones that show how to provide two way communication between a server and a client, how to detect server/client death, how to properly unregister/clean up connections), Object Linking and other 3.0 functionality. The last distribution mostly dealt with DBKit. WE ALSO NEED TO BE AWARE OF ANY BUGS in Distributed Objects.
Technical Details
Message-ID:
<1992Nov13.122410.867@hot.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!agate!linus!alliant!merk!esplanade!robertlShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!agate!linus!alliant!merk!esplanade!robertl From: Robert_La_Ferla@hot.com Subject: Distributed Objects and Network Name Server Message-ID: <1992Nov13.122410.867@hot.com> Sender: robertl@hot.com Organization: Hot Technologies Date: Fri, 13 Nov 1992 12:24:10 GMT Lines: 30