Hi, I've seen more appearances of the FCP socket freeze-up problem.
It seems this bug only affects FCP communications, and only when more than one data chunk is sent. For me, I'm only seeing the bug when connecting from an FCP client on one machine to a node on another. With small keys (which don't involve multiple DataChunks), I can't reproduce the problem. But with any key > 16k, which causes the data to be sent in multiple DataChunks, my client gets the first 16k, but the socket freezes up and won't return a single byte. I tried to replicate this behaviour by manually connecting to the FProxy port across my LAN and sending a 'GET /[EMAIL PROTECTED] HTTP/1.0', then reading the data piecemeal. No freeze-up. So it seems that either: 1) the bug is limited to FCP communication, or 2) FProxy is sending all the data in one hit So, it seems at this stage that FCP cannot be relied upon for remote connections. Ideas anyone? At the moment, I'm developing a very ambitious client, and can test it on the same host as my fred node, but I don't want to release it until FCP can be trusted to behave properly with remote connections. -- Cheers David _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
