On Thu, Apr 28, 2011 at 8:39 PM, gary clark wrote:
> 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 s
gary clark wrote:
> 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
t the moment.
Thanks,
Gary C
--- On Thu, 4/28/11, Glyph Lefkowitz wrote:
> From: Glyph Lefkowitz
> Subject: Re: [Twisted-Python] problems with transport.write
> To: "Twisted general discussion"
> Date: Thursday, April 28, 2011, 6:43 PM
>
> On Apr 28, 2011, at 4:18
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.
Try
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.
The majority of the time is sends and receives, but occasionall
