|
Check-in Number:
|
516 | |
| Date: |
2001-Jun-20 14:28:22 (local)
2001-Jun-20 12:28:22 (UTC) |
| User: | simons |
| Branch: | |
| Comment: |
Made description of what Spread does more accurate after further
testing. |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/srpc/EVAL 1.7 -> 1.8
--- EVAL 2001/06/19 17:13:40 1.7
+++ EVAL 2001/06/20 12:28:22 1.8
@@ -3,25 +3,25 @@
o Spread, http://www.spread.org/
- Spread is a sophisticated framework for distributed computing. The
- software itself is written in C and uses a design very similar to
- SRPC's: It is split into a permanently running daemon and a link
- library containing interface routines to that daemon to the
- programmer. The daemon will maintain so called "groups", which
- computers can join and leave. Furthermore the daemon provides group
- communication services based on TCP, UDP or Multicast-UPD. Via this
- communication services, the actual remote procedure calls are
- implemented.
+ Spread is a sophisticated message passing framework. The software
+ itself is written in C and uses a design very similar to SRPC's: It
+ is split into a permanently running daemon and a link library
+ containing interface routines to that daemon for the programmer. The
+ daemon will maintain so called "groups", which computers can join
+ and leave. Furthermore the daemon provides group communication
+ services based on TCP, UDP or Multicast-UPD. There is no actual RPC
+ functionality available, but implementing such a system on top of
+ Spread would be relatively trivial.
The software seems to be actively maintained, well-written and
documented, but unfortunately the following drawbacks kept us from
using it:
- - Spread's license currently prohibits any commercial use.
- But according to the authors (as of April 2001) they are providing
- special license exceptions for Open Source projects and working on
- moving Spread to a commercial split of from their University and
- then releasing Spread under a real Open Source license.
+ - Spread's license currently prohibits any commercial use, but
+ according to the authors (as of April 2001) they are providing
+ special license exceptions for Open Source projects and working
+ on moving Spread to a commercial split of from their University
+ and then releasing Spread under a real Open Source license.
- It is not possible for peers to communicate without the daemon.
(RSE: I'm not sure about this. If I understood the Spread guys
|
|
