-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 6/29/17 5:22 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
>> Subject: Re: RemoteEndpoint.Async sendText blocking
>
>> When the BIO connector is in use, you end up with
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: RemoteEndpoint.Async sendText blocking
> When the BIO connector is in use, you end up with weird things like
> this. I would switch to BIO if you want to use async.
Might want to rephrase that... Pres
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
To whom it may concern,
On 6/29/17 1:49 PM, V User wrote:
> Yes, although I admit I'm just learning about all the implications
> of that. It seemed to me that even if the actual transmission/write
> blocks indefinitely, that should be happening
Yes, although I admit I'm just learning about all the implications of that.
It seemed to me that even if the actual transmission/write blocks
indefinitely, that should be happening "asynchronously" in another thread
or something and shouldn't stop the Async version of sendText from
returning since
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Z, V, etc.,
On 6/29/17 1:16 PM, V User wrote:
> Hello! I have a question about the RemoteEndpoint.Async sendText
> method. The spec states: "Initiates the asynchronous transmission
> of a text message. This method returns before the message is
>
