The Dublin Core metadata element set
is a standard for cross-domain information resource description.
|
||
Element | Description | Value |
---|---|---|
Identifier | resource ID | http://old.zope.org/Members/tim_one/spread |
Title | resource name | Python wrapper for Spread |
Description | resource summary | This is a Python extension module wrapping the C API for Spread, an open source group communications package. The extension module was written by PythonLabs, primarily Jeremy Hylton, Guido van Rossum and Tim Peters. It is released under a <a href="./LICENSE">standard PSF open source license</a>. <p> Older releases and general information can be found at the Spread wrapper module's <a href="http://www.python.org/other/spread/">original home</a> on python.org. <h2>Requirements</h2> <p> Version 1.5 of the wrapper module is intended to be used with Spread 3.17.3. On Windows, there are two installers, one for use with the Python 2.3 line (2.3.5 is recommended), the other with the Python 2.4 line (2.4.1 is recommended). <h2>What's new in 1.5 final?</h2> <p> No changes were made since 1.5 beta 1. Compared to 1.4 final: <p> <ul> <li> Mailbox objects have a new multigroup_multicast() method, wrapping the Spread API's SP_multigroup_multicast() call. Thanks to Mark McClain for contributing code, docs, and tests for this new feature. <li> The C code was changed to suppress a nuisance warning from gcc. <li> Zope collector issue <a href="http://zope.org/Collectors/Zope/1130">1130</a>: "spreadmodule.c contains improper use of the 'sizeof' operator" <p> Spread membership messages are complicated, and before Spread 3.17 it wasn't actually possible to decode them correctly in all cases. For example, if the user changed Spread's MAX_PRIVATE_NAME, MAX_PROC_NAME, and MAX_GROUP_NAME #defines, there was no way to guess where various values began in the buffer SP_receive() was given, and segfaults or data loss could occur if you guessed wrong. <p> This wasn't entirely fixed until Spread 3.17.2 (Spread itself could still segfault if the user changed these #defines), but at least 3.17 introduced 3 new Spread API functions so that clients can determine where fields in the buffer begin. The Python Spread wrapper module has been updated to use them. <li> The module version() function is now documented. <li> Changes to the build procedure on Windows for Spread 3.17.3 were incorporated (the names of some Spread files on Windows changed to match the names of corresponding files in non-Windows builds). </ul> <h2>CVS access</h2> <p> The source code for the Python Spread wrapper module is maintained on Zope Corporation's CVS server, cvs.zope.org, under <a href="http://cvs.zope.org/Packages/Spread/">Packages/Spread</a>. <h2>Acknowledgement</h2> <p> This product uses software developed by Spread Concepts LLC for use in the Spread toolkit. For more information about Spread see <a href="http://www.spread.org">http://www.spread.org</a>. |
Creator | resource creator | tim_one |
Date | default date | 2005-01-05 00:00:00 |
Format | resource format | text/html |
Type | resource type | Software Package |
Subject | resource keywords | |
Contributors | resource collaborators | |
Language | resource language | |
Publisher | resource publisher | No publisher |
Rights | resource copyright | |
|
||
Element | Description | Value |
CreationDate | date resource created | 2005-01-05 15:19:31 |
ModificationDate | date resource last modified | 2005-06-01 11:41:47 |
EffectiveDate | date resource becomes effective | 2005-01-05 00:00:00 |
ExpirationDate | date resource expires | None |
Backlinks:
via
Google
/
Technorati
RDF:
view RDF data