Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 2 and Version 3 of Sysel/Ideas


Ignore:
Timestamp:
2010-05-23T10:37:07Z (11 years ago)
Author:
Jiri Svoboda
Comment:

Fix typo

Legend:

Unmodified
Added
Removed
Modified
  • Sysel/Ideas

    v2 v3  
    3737=== Basics ===
    3838
    39 HelenOS IPC is usually employed in an RPC-like style. Remote objects would support asynchronous messaging in the language itself. Remote object classes (and interfaces) form a separate hierarchy of inheritance to the ''local'' classes and interfaces. Remote interfaces are equivalent to IPC interfaces now usually defined in HelenOS in `uspace/lib/c/includ/ipc`. They would naturally support (multiple) inheritance. Servers contain remote classes which implement these interfaces.
     39HelenOS IPC is usually employed in an RPC-like style. Remote objects would support asynchronous messaging in the language itself. Remote object classes (and interfaces) form a separate hierarchy of inheritance to the ''local'' classes and interfaces. Remote interfaces are equivalent to IPC interfaces now usually defined in HelenOS in `uspace/lib/c/include/ipc`. They would naturally support (multiple) inheritance. Servers contain remote classes which implement these interfaces.
    4040
    4141When a client wants to use some service, they are given a reference to a remote object. This reference identifies not only the server which we talk to, but possibly also the individual resource within the server that we are accessing. For a contrived example, a console server might provide the two interfaces: