Hello,
I started looking at this point.
Here what I plan to implement:
- New Websocket Sampler using Jetty
- GUI config will have regular infos like path, host, port and a new
"method" select box which will have the following values and effect:
- connect => open connection to Websocket server & store it in
JMeterContext
- send (send message) => will use connection to send message
- close => Will close connection
- I think I will be using this library for async behaviour:
- http://code.google.com/p/guava-libraries/
It is still not clear for me what users would like to measure in these kind
of tests:
- open response time ?
- receive response time ?
- What about servers ? would they close stream on first response ? or
would they keep it open for the test ? or other option ?
Your ideas are welcome.
Regards
Philippe
On Wed, Jan 9, 2013 at 11:10 PM, Philippe Mouawad <
[email protected]> wrote:
> Ok ,
> jetty API looks clear to me.
> If nobody has an objection, it seems a good starting point.
>
> I will start something as soon as I have time.
>
> Regards
> Philippe
>
> On Sunday, January 6, 2013, Oleg Kalnichevski wrote:
>
>> On Sun, 2013-01-06 at 15:20 +0100, Philippe Mouawad wrote:
>> > Thanks Oleg, did you have the opportunity to play with it ?
>> >
>>
>> I used their CometD transport and was quite happy with it.
>>
>> > According to this:
>> > - http://webtide.intalio.com/2012/10/jetty-9-updated-websocket-api/
>> >
>> > => Requires Java 7, although I think this should not be a blocker as
>> Java 6
>> > will be in EOL within a couple of months.
>> > Only supporting WebSocket version 13 (RFC-6455) , from to what I
>> > understand, this should be fine as it seems it's the last version ?
>> > What is fine is that it should support JSR-356
>> >
>>
>> But as far as I understand that applies to Jetty 9 only, which is still
>> at an early stage of development.
>>
>> >
>> >
>> > Anyway, there seems to be a lot of projects:
>> >
>> > -
>> >
>> http://java.net/projects/websocket-spec/lists/users/archive/2012-04/message/2
>> >
>> >
>> > AHC seems to provide some portability and can use netty (which has a
>> good
>> > reputation) as underlying impl:
>> >
>> > -
>> >
>> http://jfarcand.wordpress.com/2012/05/28/writing-portable-websockets-application-using-java/
>> > - http://sonatype.github.com/async-http-client/providers.html
>> >
>> >
>>
>> My _personal_ opinion of AHC as an HTTP client is quite low. Maybe it is
>> OK as a WebSockets client, though. My advice would still be to go with
>> Jetty 8.
>>
>> Oleg
>>
>>
>>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>
--
Cordialement.
Philippe Mouawad.
