Tasks #1229

Check if spread java sources can be updated to 4.3

Added by S. Wrede over 11 years ago. Updated over 10 years ago.

Status:ResolvedStart date:11/06/2012
Priority:NormalDue date:
Assignee:J. Wienke% Done:

100%

Category:Java
Target version:rsb-0.10

Description

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.

Associated revisions

Revision 4f43186b
Added by J. Wienke over 10 years ago

fixes #1229: update spread src to 4.3

Updated spread source copy to 4.3 version with our own tcp no delay
patch.

Merge branch 'task-1229'

History

#1 Updated by J. Wienke over 11 years ago

Actually the makefile for the daemon and C library is somehow broken for the 4.2 release and doesn't install the daemon etc. Very weird.

#2 Updated by S. Wrede over 11 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.

#3 Updated by J. Wienke over 11 years ago

I think it is not compatible or at least there are some glitches. I had a problem with a client compiled against 4.1 running with 4.2.

#4 Updated by J. Moringen about 11 years ago

  • Target version changed from rsb-0.9 to rsb-0.10

#5 Updated by J. Wienke over 10 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 over 10 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?

#7 Updated by J. Wienke over 10 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 60 to 100

Applied in changeset rsb-java|commit:4f43186bd7d5d34578b4af5d94e5e058c6da4ce6.

Also available in: Atom PDF