Hi,
Cross-domain support is critical for our application, since
we'd like
to separate our content from a chatting floating window as
much as
possible and spread the traffic to two or more domains, so
each can
make best use of the two connection limits.
>From reading the cometd.js, it seems to me that
long-polling transport
does not support xdomain. While in a test I did, it actually
used long-
polling, Hi,
Cross-domain support is critical for our application, since
we'd like
to separate our content from a chatting floating window as
much as
possible and spread the traffic to two or more domains, so
each can
make best use of the two connection limits.
In the callback-polling transport, I really need the advice
handling
in the tunnelCollapse function of callbackpolling:
1. the reconnect interval needs to be respected.
2. The reconnect:handshake advice upon "Unknown
client" error
(otherwise it'll enter infinite looping)
The disconnect method of callback polling should not (IMHO)
reuse the
same code as in the longpolling transport since longpolling
uses XHR,
which will result in security violation in the case of
x-domain.
Knowing that Greg and co. are working on issues for version
1, I'm
eagerly looking forward to a robust impl soon.
Thanks a lot!
Bing
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "cometd-dev" group.
To post to this group, send email to cometd-dev googlegroups.com
To unsubscribe from this group, send email to
cometd-dev-unsubscribegooglegroups.com
For more options, visit this group at http://grou
ps.google.com/group/cometd-dev
Visit the cometd website at http://www.cometd.com/
-~----------~----~----~----~------~----~------~--~---
|
