From: <rga...@co...> - 2007-05-15 21:48:34
|
On Sun, May 13, 2007 at 08:08:38PM +0100, rga...@co... wrote: > Unfortunately this new code provokes a connection resets > from the server. Is there some basic timing rules which > we need to maintain? > > Or is it the rest of the code re-entrant enough I'm causing > scramled messages. eg:- I think I've tracked this down - I am scrambling messages due via (again I think) rentrancy, but re-entrancy thru the encryption layer causing multiple encyrpt(..) passes over the queue of unsent data. So I'm just sending the server corrupt data rather than any wierd timing foo. [ Unfortunately I've run out of time this evening to actually check whether this fixes my original bug as well. ;-). ] The downside of this is that to get this working correctly and reliably means it going to be a much more intrusive patch than I had orignally hoped - is anyone working on tidying up the internal io api ? If so it seems better to co-ordinate our efforts, (and obviously being the newbie here I don't want to step on anyones toes) or am I going it alone on this one? TTFN -- Roger. Home| http://www.sandman.uklinux.net/ Master of Peng Shui. (Ancient oriental art of Penguin Arranging) Work|Independent Sys Consultant | http://www.computer-surgery.co.uk/ New key Fpr: 1227 ABB1 7545 77A7 6816 2D18 4EBC AA9B 8EE3 1DD3 |