WebSocket is working with good performance and passing all Autobahn
tests on BIO, NIO and APR.
Currently, all three connectors using blocking IO throughout so there is
a one to one mapping between threads and connections. Therefore,
scalability is not what it could be for NIO and APR.
The remaini
On 2/28/2012 4:08 AM, Mark Thomas wrote:
WebSocket is working with good performance and passing all Autobahn
tests on BIO, NIO and APR.
Currently, all three connectors using blocking IO throughout so there is
a one to one mapping between threads and connections. Therefore,
scalability is not wha
On 28/02/2012 16:58, Filip Hanik - Dev Lists wrote:
> On 2/28/2012 4:08 AM, Mark Thomas wrote:
>> WebSocket is working with good performance and passing all Autobahn
>> tests on BIO, NIO and APR.
>>
>> Currently, all three connectors using blocking IO throughout so there is
>> a one to one mapping
On 2/28/2012 11:39 AM, Mark Thomas wrote:
On 28/02/2012 16:58, Filip Hanik - Dev Lists wrote:
On 2/28/2012 4:08 AM, Mark Thomas wrote:
WebSocket is working with good performance and passing all Autobahn
tests on BIO, NIO and APR.
Currently, all three connectors using blocking IO throughout so
On 28/02/2012 18:53, Filip Hanik - Dev Lists wrote:
> On 2/28/2012 11:39 AM, Mark Thomas wrote:
>> You may also be able to help with some problems I am having getting
>> non-blocking behaviour between messages with NIO. I'm not 100% clear
>> what is happening yet, but I think it is something like:
On 28/02/2012 21:29, Mark Thomas wrote:
> On 28/02/2012 18:53, Filip Hanik - Dev Lists wrote:
>> On 2/28/2012 11:39 AM, Mark Thomas wrote:
>
>>> You may also be able to help with some problems I am having getting
>>> non-blocking behaviour between messages with NIO. I'm not 100% clear
>>> what is
On 01/03/2012 11:31, Mark Thomas wrote:
> On 28/02/2012 21:29, Mark Thomas wrote:
>> On 28/02/2012 18:53, Filip Hanik - Dev Lists wrote:
>>> On 2/28/2012 11:39 AM, Mark Thomas wrote:
>>
You may also be able to help with some problems I am having getting
non-blocking behaviour between mess
On 3/1/2012 5:33 AM, Mark Thomas wrote:
On 01/03/2012 11:31, Mark Thomas wrote:
On 28/02/2012 21:29, Mark Thomas wrote:
On 28/02/2012 18:53, Filip Hanik - Dev Lists wrote:
On 2/28/2012 11:39 AM, Mark Thomas wrote:
You may also be able to help with some problems I am having getting
non-blockin
I have a draft patch [1] that seems to fix this. A similar change would
be required for the Comet part of Poller.processKey()
Thoughts and/or comments? Not knowing the NIO code very well, there
might be a better way to achieve the same result that I haven't seen.
Mark
[1] http://people.apache
On 01/03/2012 15:03, Filip Hanik - Dev Lists wrote:
>
>> I have a draft patch [1] that seems to fix this. A similar change would
>> be required for the Comet part of Poller.processKey()
>>
>> Thoughts and/or comments? Not knowing the NIO code very well, there
>> might be a better way to achieve th
Mark, what buffer size are you referring to increase for the web socket tests
to all pass?
Filip
On 3/1/2012 9:42 AM, Mark Thomas wrote:
On 01/03/2012 15:03, Filip Hanik - Dev Lists wrote:
I have a draft patch [1] that seems to fix this. A similar change would
be required for the Comet part o
On 01/03/2012 17:13, Filip Hanik - Dev Lists wrote:
> Mark, what buffer size are you referring to increase for the web socket
> tests to all pass?
Sorry, should have been clearer about that.
In o.a.c.websocket.MessageInbound
// 2MB - like maxPostSize
private int byteBufferMaxSize = 20971
I see, MessageInbound has hard coded receive buffers. Got it
Filip
On 3/1/2012 10:13 AM, Filip Hanik - Dev Lists wrote:
Mark, what buffer size are you referring to increase for the web socket tests
to all pass?
Filip
On 3/1/2012 9:42 AM, Mark Thomas wrote:
On 01/03/2012 15:03, Filip Hanik -
On 2/28/2012 11:39 AM, Mark Thomas wrote:
Thanks for the feedback.
You may also be able to help with some problems I am having getting
non-blocking behaviour between messages with NIO. I'm not 100% clear
what is happening yet, but I think it is something like:
- HTTP GET (with upgrade request ar
On 01/03/2012 18:01, Filip Hanik - Dev Lists wrote:
> Alright, now that I'm all squared away with Autobahn and test cases
> running. Is there a specific unit test you have to produce this behavior?
> That would help me for digging through it.
Assuming you are running trunk, then what you'll curren
On 01/03/2012 18:00, Filip Hanik - Dev Lists wrote:
> I see, MessageInbound has hard coded receive buffers. Got it
They are configurable, they just aren't currently configured. I've been
meaning to apply a patch that would add some commented out configuration
to the examples webapp so it can just
On Thu, Mar 1, 2012 at 9:54 AM, Mark Thomas wrote:
> On 01/03/2012 17:13, Filip Hanik - Dev Lists wrote:
> > Mark, what buffer size are you referring to increase for the web socket
> > tests to all pass?
>
> Sorry, should have been clearer about that.
>
> In o.a.c.websocket.MessageInbound
>
>
On 01/03/2012 18:22, Costin Manolache wrote:
> On Thu, Mar 1, 2012 at 9:54 AM, Mark Thomas wrote:
>
>> On 01/03/2012 17:13, Filip Hanik - Dev Lists wrote:
>>> Mark, what buffer size are you referring to increase for the web socket
>>> tests to all pass?
>>
>> Sorry, should have been clearer about
hi Mark, sorry, I know you posted this earlier, thanks for reposting it to set
me straight.
Yes, it can make sense that you see the behavior you are. But in "theory" you
shouldn't.
If you call readSocket(false,bytes,off,maxRead), all the socket does is that it checks in the OS socket buffer to
On 01/03/2012 22:55, Filip Hanik - Dev Lists wrote:
> You can't register on a selector using another thread.
Bingo. That explains it. Is that documented anywhere? I don't recall
reading it but I may well have missed it. Looking at the code, it looks
like HTTP would have been unaffected which is go
On 3/2/2012 2:13 AM, Mark Thomas wrote:
You can't register on a selector using another thread.
Bingo. That explains it. Is that documented anywhere?
I'm not sure if the java.nio documentation says it, I think it does. The Selector object is not thread safe. trying to manipulate
interestops and
On 2/03/2012 2:29 PM, Filip Hanik - Dev Lists wrote:
On 3/2/2012 2:13 AM, Mark Thomas wrote:
You can't register on a selector using another thread.
Bingo. That explains it. Is that documented anywhere?
I'm not sure if the java.nio documentation says it, I think it does.
The Selector object is
Speaking of thread safety, in the APR connector, when SSL is used, it may
be possible to hit some problems if read and write are called at same time
from different threads on same socket - SSL_read and SSL_write share the
same context and apparently are not safe.
I don't know if websocket allows a
On 08/03/2012 09:12, Johno Crawford wrote:
> What's next / left on the TODO list Mark? Anything I can help out with?
Porting the generic HTTP upgrade followed by the WebSocket code to
7.0.x. I don't think there is much for you to do there.
WebSocket needs some documentation. My plan was to keep i
On 8/03/2012 9:10 PM, Mark Thomas wrote:
On 08/03/2012 09:12, Johno Crawford wrote:
What's next / left on the TODO list Mark? Anything I can help out with?
Porting the generic HTTP upgrade followed by the WebSocket code to
7.0.x. I don't think there is much for you to do there.
WebSocket needs
On 14/03/2012 10:15, Johno Crawford wrote:
> On 8/03/2012 9:10 PM, Mark Thomas wrote:
>> On 08/03/2012 09:12, Johno Crawford wrote:
>>> What's next / left on the TODO list Mark? Anything I can help out with?
>> Porting the generic HTTP upgrade followed by the WebSocket code to
>> 7.0.x. I don't thi
On 3/14/2012 8:14 AM, Mark Thomas wrote:
On 14/03/2012 10:15, Johno Crawford wrote:
On 8/03/2012 9:10 PM, Mark Thomas wrote:
On 08/03/2012 09:12, Johno Crawford wrote:
What's next / left on the TODO list Mark? Anything I can help out with?
Porting the generic HTTP upgrade followed by the WebS
27 matches
Mail list logo
