On 13 May 2013, at 12:26, Pavel Bucek <pavel.bucek_at_oracle.com> wrote:
> Hi Gerard,
>
> I have something like it locally, I guess I can tidy it up and commit to the trunk.
Sure, that would be a good start.
>
> Do you have some set of features which should be included? My command line client can connect to ws:// uri, send and receive text messages (non-interactive at the moment, that could be improved by using Jline.. but there might be licensing issues) and thats it.
Of the top of my head whilst my lunchtime walk:
1) Connect / Disconnect from particular ws:// URI
2) Have proper history and key completion. (Hence JLine, license is here - BSD so should be okay Modified BSD License)
3) Be able to queue incoming messages / or display them as they arrive
4) Send text / then binary
It should only be a few command to achieve this, based on what I have seen of the client in web socket this should be easy once the threading of display of local messages is dealt with.
I guess let me see your code, and I will have a fiddle see what I can come up with. I would welcome suggestions for alternatives to JLine 2.x if they are available as it is lacking in the command parsing aspect. (Cliche is better but not in Maven and doesn't do the command history stuff)
I might have some follow up questions about using Tyrus as a proxy between a client and a service later on as I work on tooling. Is this something you have considered as a use case?
Thanks, hope you had a nice break. :-)
Gerard
>
> Thanks,
> Pavel
>
> On 5/13/13 12:28 PM, Gerard Davison wrote:
>> All,
>>
>> Are they any good command line testing tools for interacting with WebSocket services for testing purposes? If not then I will knock one up using the tyrus API and something like Jline2 to deal with the terminal issues.
>>
>> Thanks,
>>
>> Gerard
>>
>