Tracing data coming out the tcp connection and contrasting with what's coming out the client side makes it clear where the bug lies. Not only that capturing the data in the form which is causing the client side to bork (chunks et al) means the problem should be repeatable now and hence reliably fixable :-D
Tracing data coming out the tcp connection and contrasting with what's coming out the client side makes it clear where the bug lies. Not only that capturing the data in the form which is causing the client side to bork (chunks et al) means the problem should be repeatable now and hence reliably fixable :-D
sparkslabs/kamaelia,sparkslabs/kamaelia,sparkslabs/kamaelia,sparkslabs/kamaelia,sparkslabs/kamaelia,sparkslabs/kamaelia,sparkslabs/kamaelia,sparkslabs/kamaelia,sparkslabs/kamaelia,sparkslabs/kamaelia