Much appreciated on the quick response.
It fails by writing a large string at the server side and not receiving any data at the client. The client uses open-ssl and is blocking to receive data. I dont know if its possible to determine if the write was successful or not on the server side i.e knowing how many bytes were written etc. I dont see any exceptions. The connection is still maintained and like I said its intermittent. So when a transport.write occurs is there an api I can use to see if it was successful?
I'm trying to isolate if its a server problem or a client issue at the moment.
--- On Thu, 4/28/11, Glyph Lefkowitz firstname.lastname@example.org wrote:
From: Glyph Lefkowitz email@example.com Subject: Re: [Twisted-Python] problems with transport.write To: "Twisted general discussion" firstname.lastname@example.org Date: Thursday, April 28, 2011, 6:43 PM
On Apr 28, 2011, at 4:18 PM, gary clark wrote:
Hiya, I have created a client-server application which uses
ssl to communicate.
I am trying to determine if its the server or client.
However its definetly sending a string in the connection.transport.write to the target client.
Trying to determine what is the server or the client?
The majority of the time is sends and receives, but
occasionally it fails.
Is there a way (other than the client sending an ACK
with a sequence number in it) to know if the write was successful and if not resend.
If you're using SSL, then you're using TCP, which transparently _does_ send an ACK with a sequence number in it. You never have to re-send TCP segments at the application layer, that would result in a stream with duplicate data in it.
Please be more specific about the problem you're having, so we can find an answer :).
Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python