A couple guys got a websocket-over-flash implementation working, which
should work in any browser that supports flash. I don't know what the
status of that is though. If there's still no movement on that, I
might take a look at patching in their changes myself in a couple
weeks.

At the moment, websockets are only supported in Firefox 4, Chrome and
Safari. Last I checked, IE9 might not ship with websocket support.

-J

On Wed, Oct 13, 2010 at 11:56 PM, Alex North <[email protected]> wrote:
> Google Wave does not use websockets, correct. It uses a comet-like long
> polling. For the moment the WIAB client is websockets or nothing, but
> there's no practical reason why it couldn't also use a standard HTTP-based
> transport. It's just a matter of coding. We're not focussing on that right
> now though.
> Hope that helps,
> Alex
>
> On 13 October 2010 23:27, James Purser <[email protected]> wrote:
>>
>> Not exactly sure what wave.google.com is using though given that it works
>> with different browsers I'm thinking it doesn't use websockets.
>> James
>>
>> On Wed, Oct 13, 2010 at 11:26 PM, Toby Ashley <[email protected]> wrote:
>>>
>>> James - am I right in thinking that the client at wave.google.com is
>>> using long-polling, rather than websockets?
>>> Does the version of the client being discussed here also work with
>>> long-polling, or is it websockets or nothing?
>>>
>>>
>>> On Wed, Oct 13, 2010 at 1:22 PM, James Purser <[email protected]>
>>> wrote:
>>>>
>>>> Okay, for the moment it's best to use Chrome as it has the most
>>>> compatible version of websockets.
>>>>
>>>> On Wed, Oct 13, 2010 at 11:13 PM, BuggyB <[email protected]> wrote:
>>>>>
>>>>> I use the browser Firefox.
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Wave Protocol" group.
>>>>> To post to this group, send email to [email protected].
>>>>> To unsubscribe from this group, send email to
>>>>> [email protected].
>>>>> For more options, visit this group at
>>>>> http://groups.google.com/group/wave-protocol?hl=en.
>>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Wave Protocol" group.
>>>> To post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to
>>>> [email protected].
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/wave-protocol?hl=en.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Wave Protocol" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to
>>> [email protected].
>>> For more options, visit this group at
>>> http://groups.google.com/group/wave-protocol?hl=en.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Wave Protocol" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to
>> [email protected].
>> For more options, visit this group at
>> http://groups.google.com/group/wave-protocol?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Wave Protocol" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/wave-protocol?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en.

Reply via email to