Hi,

Thanks for that. The reason I included the foreign library was that it
seemed to simple on the client side to matter. If I recall correctly (not at
the right computer now) it simply writes the frame delimiters and the data
to a buffered output stream and then flushes which seemed simple enough to
me.

(Also this is due to a scenario when we where integration-testing our server
- http://www.cubeia.com/index.php/products/firebase - and everything else
works except this one scenario).

But I'll have a look at your tests and see what happens.

/Lars J. Nilsson


On Wed, Oct 12, 2011 at 2:33 PM, Simone Bordet <[email protected]> wrote:

> Hi,
>
> On Wed, Oct 12, 2011 at 14:24, Thomas Becker <[email protected]> wrote:
> > Hi Lars,
> >
> > thanks for providing the test case. However we've some loadtests as well
> and
> > they have a similar setup without using a foreign client library like
> your
> > test and they all work fine. For instance "WebSocketLoadD13Test.java" in
> > jetty8.
> >
> > If you can provide a test without using a foreign library and using
> jetty's
> > api only, then we'll do some further investigations. Until then we
> presume
> > that the issue is in the library you use as we've working load tests for
> > jetty and cometd.
>
> For the record, we have made benchmarks up to 50k websocket messages/s
> without issues, see
> http://webtide.intalio.com/2011/09/cometd-2-4-0-websocket-benchmarks/.
>
> Also, the library you use does not seem up-to-date with the latest
> drafts that, for example, define a close code and close description to
> be exposed in the API.
> Jetty's WebSocket APIs are up to date with the latest drafts, so
> sticking with Jetty's libraries will probably solve all your problems.
>
> Simon
> --
> http://cometd.org
> http://intalio.com
> http://bordet.blogspot.com
> ----
> Finally, no matter how good the architecture and design are,
> to deliver bug-free software with optimal performance and reliability,
> the implementation technique must be flawless.   Victoria Livschitz
> _______________________________________________
> jetty-users mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to