|July 27, 1999
Spread Version 3.11 Relased with Source Code
New version of Spread released. First version with Source code included!.
|July 8, 1999
Created Separate Spread website and started enhancing it.
|July 5, 1999
Final version of the Spread license is available.
Please email email@example.com if you have any concerns or questions.
|May 26, 1999
Release Version 3.10
- Expiration Date Removed from Binary version.
This release of the executables will not expire.
- New Copyright Statement
The copyright of Spread has been finalized. The statement at the top of this file shows it.
- Source release soon & new license
- As soon as a few final issues are resolved we will release the source to Spread under the CNDS Non-Commercial License.
- A draft of the new license can be found at http://www.spread.org/license/. Please email us any comments or concerns you have at firstname.lastname@example.org
- Bugs Fixed:
- Bug fix to the SP_scatter_recv() call to make receives into scatter structures of multiple entries of different sizes work.
- The Linux platform also had scatter-gather functionality enabled (now that glibc has working sendmsg, recvmsg calls)
- Fixed bug where packets which are delayed a long time in the network but then actually arrive at a spread daemon cause a crash.
Release Version 3.9
Libsp.a has split into two libraries, libsp.a and libtsp.a, they
are identical except that libtsp.a is thread-safe and libsp.a is not.
Both versions are provided so that single-threaded programs who don't
need a safe library can avoid the (admittedly pretty small) overhead of
locking. The libtsp.a can be used identically with libsp.a with the
addition that all SP_* functions can be called by multiple threads
at the same time. Thread safety in libtsp.a is provided optimally,
with the most possible parallelism allowed. Threads acting on separate
mailboxes will never block each other, threads writing to a mailbox will
never block other threads reading from the same mailbox and vice versa.
The one time thread calls to SP_ functions will be serialzed is when
multiple threads are reading the same mailbox or writing the same mailbox.
There is minimal locking of internal structures which can temporarily
block another thread, but since a thread never blocks while in one of these
structure critical sections and the duration of the lock is at most a few
instructions the delay should be minimal.
Spread now allows you to specifiy IP-Multicast addresses(i.e. 220.127.116.11) as
the broadcast address for a segment in the config.dat file. This will work
transparently in the same segment, and is guaranteed not to spill multicast
packets beyond that segment. If multi-segment ip-multicast is desired,
please contact us.
- Fixed several minor bugs.
- Included man pages for SP functions. The old html documentation is also
- None of these changes effect the Java version which has not changed.