 |
JXTA-C 2.4 "Kenting" Release Summary
Implementation Compatibility Testing
During this release cycle JXTA-C has undergone extensive compatibility
testing with the JXTA-JSE, JXME JXTA Micro Edition CLDC/MIDP and CDC
implementations. We've made significant progress all around as a
result of this effort and the assistance of the JXTA-JSE and JXME
developers and community has been very much appreciated.
In recent tests we have been able to successfully exercise all basic
JXTA functionality with diverse mixed networks of implementations and
configurations. For future releases we hope to further extend the JXTA
functionality across the multiple implementations and configurations
and further improve performance and interoperability.
Acknowledgments
Special thanks to all of the community members who have contributed
ideas, reported problems, provided patches, and have helped greatly to
improve the quality, and robustness of this release.
Particularly for this release:
- Stefan Lankes
(lankes), Ruben Niedehagen and Stephan Gsell: contribute the .NET binding for JXTA-C.
- Rick Keiner
(exocetrick): Tunability code.
- Eric Xu
(mmx2005): MSA/MCA implementation and various improvements.
New Features & Significant Changes
Tunability
Several core services have some parameters hardcoded in the program,
now those parameters can be modified with program or in the
PlatformConfig file.
.NET binding
Now you can use jxta-c in .NET if you like, the binding is ready to
use on both Microsoft platform or with Mono. This feature is still
experimental, as the API might change in the future.
Endpoint enhancement
A new negative cache policy is implemented in endpoint service to have
a quicker response time under a ad-hoc environment by using
exponential timeout rather than a fixed timeout. See the new policy
at: http://wiki.java.net/bin/view/Jxta/JxtaCNegativeCache
jpr_threadonce removed
jpr_threadonce was a wrapper around apr_threadonce, now code in jxta-c
using threadonce are replaced with jxta_initialize/jxta_terminate, and
the function is now removed.
Downloading and Installing
You can download the dist tarball from:
http://download.jxta.org/build/release/c/2.4/
or alternatively directly access CVS.
The instruction on how to build JXTA-C can be found at:
http://wiki.java.net/bin/view/Jxta/HowToBuildJXTA-C
We are looking for people to maintain binary build for their favorite
OS, please let us know if you want to contribute.
<mailto:discuss@jxta-c.jxta.org>
Known incompatibilities between JXTA-C 2.4 and prior JXTA-C 2.x releases
- jpr_threadonce removed: If your code make use of those APIs(chances are low), you will need to modify your code.
Issued Closed During JXTA-C 2.4
| 57 | DEFECT | P2 | API comments incorrect: jxta_dq.h |
| 226 | DEFECT | P2 | Misconfigure relay and http transport cause segment fault |
| 126 | DEFECT | P3 | multiple rdv seeds |
| 132 | DEFECT | P3 | rdv connection lost |
| 221 | DEFECT | P3 | custom service cleanup on exit |
| 225 | DEFECT | P3 | Segmentation fault in jxta_relay.c |
| 227 | DEFECT | P3 | Can't process peerview message in subgroups |
| 228 | DEFECT | P3 | Incompatibility between SRDI in JXTA-C and JXTA-JSE |
| 229 | ENHANC | P3 | enhancement for endpoint negative cache |
| 231 | ENHANC | P3 | endpoint service to support message sending in both sync/asy |
To see a complete list of fixes, please refer to the ChangeLog file.
Known issues in JXTA-C 2.4
| 162 | DEFECT | P3 | peer lost RDV connection after joined to a subgroup for a while |
| 193 | DEFECT | P3 | Not access to Jxta_service and Jxta_module structures |
| 219 | DEFECT | P3 | method of Removing Expired PVEs is wrong |
| 223 | DEFECT | P3 | relay connection lost |
| 233 | DEFECT | P3 | Default setting should not be write into PlatformConfig |
You can see a full list of currently open issues for JXTA-C at following URL:
http://jxta-c.jxta.org/issues/buglist.cgi?issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED
|