Dammit, I spoke too soon. Realised that I'd run the FCP test suite talking to node build 5013.
Reverted to node build 5028, now running over Java 1.4.2, and the tests froze in the same place - awaiting the data following the second 'DataChunk' header in response to an 'FECEncodeSegment' command. So sorry to say, dear Freenet node developers, there's still a bug somewhere in the node code. More details about my setup: - node running over Sun JDK 1.4.2, in Debian Woody on AMD K62/500 - client running on a different machine on the LAN (deb unstable) - no observable TCP/IP stack issues with any other software on the two machines Running the testsuite on the same machine, problem does not show. Running node build 5013, problem does not show, regardless of which machine the client is running. Again, something has crept into the node code between build 5013 and 5028 which is causing this fatal weirdness. Clues? Other client writers - can you please test FCP FEC Splitfiles insertion, making sure to run your client on a different machine? I'd be interested to know if this bug is biting you as well. -- Cheers David _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
