On Tue, Nov 6, 2018 at 4:51 PM, Chris Withers wrote:
> On 06/11/2018 13:47, Jean-Paul Calderone wrote:
>
>> Thanks, but the special bit I was asking about is having my
>> application's logical flow pause until the websocket is successfully
>> up
>> and a successful response has been r
On 06/11/2018 13:47, Jean-Paul Calderone wrote:
Thanks, but the special bit I was asking about is having my
application's logical flow pause until the websocket is successfully up
and a successful response has been received, all without blocking the
reactor.
How do I do that?
On Tue, Nov 6, 2018 at 6:42 AM Chris Withers wrote:
> On 05/11/2018 18:32, meejah wrote:
> > Chris Withers writes:
> >
> >> So, separate question: I have a client that's making a connection to a
> >> websocket from a server. The client needs to send an "auth" message
> >> once the websocket is u
On 05/11/2018 18:32, meejah wrote:
Chris Withers writes:
So, separate question: I have a client that's making a connection to a
websocket from a server. The client needs to send an "auth" message
once the websocket is up, and the client code shouldn't progress until
it receives an affirmative
Chris Withers writes:
> So, separate question: I have a client that's making a connection to a
> websocket from a server. The client needs to send an "auth" message
> once the websocket is up, and the client code shouldn't progress until
> it receives an affirmative response. How do I do this in
Hi Again,
So, separate question: I have a client that's making a connection to a
websocket from a server. The client needs to send an "auth" message once
the websocket is up, and the client code shouldn't progress until it
receives an affirmative response. How do I do this in a non-blocking wa
