On Jul 7, 2016, at 7:10 AM, peter royal <peter.royal(a)pobox.com>
wrote:
I looked some more and cancellation would be a huge change - I'm going
to see how far I can get by using the existing callback for flow
control.
-pete
--
(peter.royal|osi)(a)pobox.com -
http://fotap.org/~osi
> On Wed, Jul 6, 2016, at 09:43 PM, Stuart Douglas wrote:
> Some of the methods take a WebSocketCallback that will notify you on
> completion or error, however at the moment there is no way to cancel a
> message.
>
> Stuart
>
> On Thu, Jul 7, 2016 at 6:56 AM, peter royal <peter.royal(a)pobox.com>
> wrote:
>> I am finding that sometimes I have WebSocket connections that are unable
>> to flush messages out the socket at the rate I am generating messages.
>>
>> I'm using the core.WebSockets class to send messages. Is it possible to
>> achieve this with what exists currently? My initial guess is no..
>> conceptually it would be nice for core.WebSockets to return a
>> CompletableFuture-style object that would let me get a callback when the
>> message is sent, or have the ability to cancel it if it is still sitting
>> in the send queue.
>>
>> I'm happy to help build something into Undertow if it is a welcome
>> addition.
>>
>> -pete
>>
>> --
>> (peter.royal|osi)(a)pobox.com -
http://fotap.org/~osi
>> _______________________________________________
>> undertow-dev mailing list
>> undertow-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/undertow-dev
_______________________________________________
undertow-dev mailing list
undertow-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev