Check if spread java sources can be updated to 4.3
|Assignee:||J. Wienke||% Done:|
From the Spread mailing list:
Since you are using Spread 4.1, this may be a fixed problem. The Spread 4.2 release that came out in June has a number of fixes (especially to the Java API) which solved a number of deadlock, disconnection and crash bugs.
Sounds like a worthwhile effort.
#2 Updated by S. Wrede almost 9 years ago
This is indeed strange. We should post a message to the Spread ML after we tested that with a current download. If the protocol implemented in the Java binding is backwards compatible (which I'd expect at least to version 4), we could upgrade at least the Java source.
#5 Updated by J. Wienke about 8 years ago
- Subject changed from Check if Spread Source in RSBJava is or can be updated to Spread 4.2 to Check if spread java sources can be updated to 4.3
- Status changed from New to In Progress
- Assignee set to J. Wienke
There are some parts left in our version of spread. I will report these changes upstream.
#6 Updated by J. Wienke almost 8 years ago
- % Done changed from 0 to 60
As there seems to be no immediate reaction from the spread guys I have created a feature branch with an upgraded version of the spread source (4.3) including the tcpNoDelay patch we had before. See branch task-1229. Unit tests run without problems even when running against a 4.2 daemon.
Any objections wrt merging this branch back to master?