The problem seems to be that the server is supposed to send a couple more confirmation packets, but does not for 5 minutes. So the client is correct in waiting: it has not received the last few packets of the transaction yet, even though it has received the actual xmlrpc data.
I have seen a couple of posts on the internet about the "socket.error: (98, 'Address already in use')" problem, but have never seen an explanation or solution. Has anyone run into this problem? On Mar 4, 1:53 pm, Wichert Akkerman <[email protected]> wrote: > Previously Bryan wrote: > > Using wireshark on the client side, the xmlrpc data is actually > > getting back to the client right away. Then there is the large pause > > (always right around 5 minutes) > > Perhaps you are sending an incorrect Content-Length header and the > client is waiting for more data to arrive? > > Wichert. > > -- > Wichert Akkerman <[email protected]> It is simple to make > things.http://www.wiggy.net/ It is hard to make things > simple. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
