Oberon ||
Library ||
Module Index ||
Search Engine ||
Definition ||
Module
Ulm's Oberon Library:
RemotePersistentObjects
NAME
RemotePersistentObjects - delegation of PersistentObjects.Write to remote objects
SYNOPSIS
PROCEDURE Init(object: PersistentObjects.Object);
PROCEDURE RegisterType(VAR type: Services.Type;
name, baseName: ARRAY OF CHAR);
DESCRIPTION
RemotePersistentObjects
allows the PersistentObjects.Write operation to
be delegated from proxy objects to the associated remote object.
Note that this technique causes the stream parameter
which is passed to PersistentObjects.Write to be
exported to the side of the original object (see RemoteStreams).
Both operations are to be called by that module which
offers the RemoteObjects service for the object type
of those objects which are to be supported by RemotePersistentObjects.
RegisterType is to be called instead of
PersistentObjects.RegisterType for the proxy object type
during the initialization time.
Init is to be called on the exporting side by
the getParams interface procedure of RemoteObjects.
DIAGNOSTICS
RemotePersistentObjects does not generate any errors itself.
See Streams, RemoteObjects,
and PersistentObjects for possible failures.
SEE ALSO
- PersistentObjects
-
conversion of objects into a sequence of bytes and vice versa
- RemoteObjects
-
access of remote objects
- RemoteStreams
-
RemoteObjects service provider for streams of Streams
BUGS
Currently, NetIO operations are not delegated from
a proxy stream to the original stream.
Consequently, RemotePersistentObjects works only as expected if
- the remote side has the same hardware architecture as the local side, and
- the local side hasn't overridden the default interface of NetIO
for the stream which is passed to PersistentObjects.Write.
Edited by: borchert, last change: 2000/09/12, revision: 1.2, converted to HTML: 2000/09/12
Oberon ||
Library ||
Module Index ||
Search Engine ||
Definition ||
Module