|
Check-in Number:
|
496 | |
| Date: |
2001-Jun-12 15:14:48 (local)
2001-Jun-12 13:14:48 (UTC) |
| User: | simons |
| Branch: | |
| Comment: |
Updated milestones. |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/srpc/TODO 1.2 -> 1.3
--- TODO 2001/05/22 14:38:26 1.2
+++ TODO 2001/06/12 13:14:48 1.3
@@ -1,25 +1,59 @@
-Efficient RPC (E-RPC)
-=====================
+Simple RPC
+==========
Architecture:
-- libeprc
-- libserialize
+- 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) [02-Jul-2001]
+
+o M2 (peti+rse) [25-Jun-2001]
- design/architecture paper (authentication+encryption framework)
(< 10KB Text + 1x Figure)
- - rpc protocol (ohne serialization)
- (< 5KB Text)
- - API specification (erpc.h, serial.h)
-o M3 (peti)
- - source tree
- - implementation
-o M4 (rse)
- - OSSP integration/adjustierung
-o M5 (peti)
+
+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
|
|
ossp-pkg/xds/TODO 1.2 -> 1.3
--- TODO 2001/05/22 14:38:26 1.2
+++ TODO 2001/06/12 13:14:48 1.3
@@ -1,25 +1,59 @@
-Efficient RPC (E-RPC)
-=====================
+Simple RPC
+==========
Architecture:
-- libeprc
-- libserialize
+- 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) [02-Jul-2001]
+
+o M2 (peti+rse) [25-Jun-2001]
- design/architecture paper (authentication+encryption framework)
(< 10KB Text + 1x Figure)
- - rpc protocol (ohne serialization)
- (< 5KB Text)
- - API specification (erpc.h, serial.h)
-o M3 (peti)
- - source tree
- - implementation
-o M4 (rse)
- - OSSP integration/adjustierung
-o M5 (peti)
+
+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
|
|
