Simple RPC
==========

Architecture:
- Abstracted Message Passing Library: libamp
- eXtendable Data Serialization Library: libxds
- Simple Remote Procedure Call Library: libsrpc

TODO:

- The server actually performing the function call has to interpret
  the transferred data according to the functions prototype. This may
  be done in one of the following ways:

   - All functions have the same prototype. The function may then be a
     stub calling the actual function. These stubs can be generated
     manually or semi-automatically.

   - Allow only a finite set of prototypes and switch according to the
     function tye, like in eAPI in Apache.

   - Build function call dynamically using the Foreign Function Call
     library.

- The programmer should be able to specify whether his implementations
  need guarantees of being called at least once, exactly once, etc.


o M1 (peti) [11-Jun-2001]
  - evaluation (-> ideas)
    (checklist)
  - prototype
    (C++)

o M2 (peti+rse) [25-Jun-2001]
  - design/architecture paper (authentication+encryption framework)
    (< 10KB Text + 1x Figure)

o M3 (peti+rse) [9-Jul-2001]
  - design libxds API
  - design libamp API
  - preliminary design libsrpc API

o M4 (peti)
  - implementation of libxds
  - implementation of libamp

o M5 (peti+rse)
  - design libsrpc API and protocol

o M6 (peti)
  - implementation libsrpc
  - implementation xxxd

o M7 (peti)
  - documentation

o M8 (rse)
  - OSSP integration