Well, from a grizzly perspective, I'm more interested in having 3rd
party apps hit the server. The client (which really is just a naive
port of the comet version) isn't as imperative to get completely
complaint at this point. At the moment, we only support a text frame
but I plan to expand what's supported now that the infrastructure is
there and working. I'm working on more unit tests (and a basic
websocket client API) to pound the server and shake things and binary
frames are on the list to implement.
I have a couple of grizzly/glassfish bugs to work so it might be a day
or two before I can get back to it but i'm hoping to have some more
significant progress by end of week.
On 3/1/10 10:05 AM, Arman Djusupov wrote:
> Shall we create a .NET client that communicates with your chat
> application server, as well as a .NET server for your chat app client?
> Do you support binary frames or only text frames?
>
> With best regards,
> Arman
>
> Justin Lee wrote:
>> I would love some interop testing. I've tested with the sample app
>> (a port of the comet-chat app) and some basic google chrome stuff,
>> but it really needs other eyes at this point to make sure i'm not
>> missing something.
>>
>> On 2/26/10 4:07 AM, Arman Djusupov wrote:
>>> Hello Justin,
>>>
>>> We have a working Web Socket implementation for WCF. If you Grizzly
>>> implementation is in a ready enough state, shall we do some interop
>>> testing?
>>>
>>> With best regards,
>>> Arman
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>