On 19/12/2007, Arnaud Simon <[EMAIL PROTECTED]> wrote: > > On Wed, 2007-12-19 at 13:32 +0000, Robert Godfrey wrote: > > Hi Arnaud, > > > > never seen that message before, an we do a lot of development / > > testing on Windows (XP SP1 / 2). > > > > have you got any way to trace what you are sending over the wire... > > > > Are you using the string "payload-message" anywhere in your code? > > > The test is using a byte message which content is set from the string > "-message payload-message paylaod-message payload-message paylaod". I'll > investigate further, that may be an issue with my Windows client or with > my network. Strangely enough I have seen such an issue with the 0.10 > client. I'll try with a real M2 client first. > > Thanks > > Arnaud >
Given we've never seen anything like this in M2 -> M2 -> M2 setups, my first guess would be an issue in the encoder / decoder in the 0-10 client... -- Rob
