Re: [jetty-users] connection.close() immediately after connection.send(S

[Brandon Mintern <mintern@xxxxxxxxxxx>]

Diving into the source, it looks like it is asynchronous, and that
frames are added to a generator's WebSocketBuffers Buffer object. I
assume that the idea is that a Close frame will be added to the
buffer(s) after all Send frames have been added, ensuring proper
ordering. Might there be some race condition in here where a Close
frame could be inserted into an improper location in the buffers?

Just to be clear, my code in question is effectively:

connection.sendMessage(ratherLargeString)
connection.close()

so the problem is not there.

On Wed, Oct 31, 2012 at 3:05 PM, Brandon Mintern <mintern@xxxxxxxxxxx> wrote:
> On Wed, Oct 31, 2012 at 2:52 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
>>
>> Which version of Jetty?
>
> It's jetty-websocket-8.1.7.v20120910