GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  NETOBJD (1)

NAME

netobjd - the Network Object agent daemon

CONTENTS

Syntax
Description
Documentation
Restrictions

SYNTAX

netobjd &

DESCRIPTION

The Network Objects package provides a simple but powerful facility for remote method invocation in the context of Modula3. Under Network Objects, all subtypes of the object type NetObj.T are treated specially in that they can be passed to remote address spaces by reference. This remote reference appears at the destination as a surrogate object which is a subtype of the original object type. If the original type has methods, these methods can be remotely invoked through the surrogate.

The netobjd program provides a mechanism to publish objects for use by other address spaces. It implements a table which maps textual into objects. A service provider, for example, might advertise its service by registering an object with netobjd under some well-defined name. Similarly, a client might gain access to this service by retrieving the server’s object from the netobjd insatnce on the server’s machine.

There should be only one instance of netobjd per machine. This one instance is the machine-wide default agent for all imports and exports of network objects.

The netobjd program listens on a well known socket (currently TCP socket 9786) for incoming requests.

DOCUMENTATION

A reference manual (SRC Research Report 115) can be found in:
/proj/doc/NetObjMan.ps

RESTRICTIONS

Since netobjd is often run in background, it is easy to forget that an instance is running. The second instance of netobjd will fail with a TCP error when it attempts to open its listener socket.

If an instance of netobjd dies, all of the objects that were registered in its table are lost. There currently is no standard mechanism for restarting netobj after a failure. Even if netobjd is restarted, there is currently no stable record of the objects held by previous instantiations.

AUTHOR

Ted Wobber

Copyright 1994 Digital Equipment Corporation.
Distributed only by permission.

Last modified on Thu May 12 15:53:47 PDT 1994 by wobber

Search for    or go to Top of page |  Section 1 |  Main Index


NETOBJD (1) -->

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.