On Jul 27, 2013, at 3:12 PM, gary clark wrote:
> Ok finally fixed the damn thing. I made the packets smaller and created a
> task in the .tac file to call a routine that send the message parts piece by
> piece.
>
> Thanks,
> Gazza
>
That's the wrong way to implement that. You can't rely
Ok finally fixed the damn thing. I made the packets smaller and created a task
in the .tac file to call a routine that send the message parts piece by piece.
Thanks,
Gazza
From: gary clark
To: gary clark ; Twisted general discussion
; Twisted general discussion
Sent: Saturday, July 27, 20
Ok split my data up into smaller fragments. It still look like its reassembing
the whole payload
before sending it to the client. I'm calling transport.write(partdata) multiple
times with a 0.5 second delay running in a twisted thread. How can I force the
write to happen straight away in twisted
Guys,
Its the MTU size. Anything bigger than 1500 bytes is getting fragmented.
Using wireshark I'm seeing TCP Previous segment lost anything bigger than 1500.
However once that
happens things go south and remain there.
Oh boy one day I will learn but not today.
Cheers,
Gazza
From: "exar...
On 04:08 pm, burslem2...@yahoo.com wrote:
Hello,
This problem has been driving me crazy for a couple of days. I'm hoping
someone can shed some light
on this. I have a twisted server its using open-ssl (using
certificates) and runs on linux and communicates great with a windows
client thats se
Hi Gary,
On Sat, Jul 27, 2013 at 6:08 PM, gary clark wrote:
> Hello,
>
> This problem has been driving me crazy for a couple of days. I'm hoping
> someone can shed some light
> on this. I have a twisted server its using open-ssl (using certificates)
> and runs on linux and communicates great wit
Hello,
This problem has been driving me crazy for a couple of days. I'm hoping someone
can shed some light
on this. I have a twisted server its using open-ssl (using certificates) and
runs on linux and communicates great with a windows client thats send messages
every second.
However when I
On Sat, Jul 27, 2013 at 5:26 AM, Glyph wrote:
>
> On Jul 26, 2013, at 7:12 AM, exar...@twistedmatrix.com wrote:
>
> To address this problem, I suggest you get into the habit of watching your
> unit tests fail in the expected way before you make the necessary
> implementation changes to make them
