How does the Xsi Events go to the subscriber through NAT?
If the subscriber doesn't know its public IP or can't be allowed to set router for port forwarding, Xsi Events will not go to the subscriber through NAT. Is there any workaround for this issue? Thanks!
Posted Answers
Paul,
in a nutshell, at the moment you need to use an intermediate application (ie. perhaps the same proxy you use today in order to avoid cross-site scripting driven security restrictions within browsers) that has a public IP address, performs the subscriptions on behalf of clients. The clients can then use AJAX long polling or similar as a mechanism to open a channel to this relay and receive events back.
Roger.
Posted: Jan 21, 2010
Although in R17 out this spring we will support Apache COMET that allows you to keep a persistent HTTP connection to solve this issue.
Posted: Jan 21, 2010
Thank you for response, guys!
If I want to use Xsi for most of use case, and use CAP to subscribe events only, is that feasible? May i use both protocols to connect to all deployed servers in the same time?
Thanks! Paul
Posted: Feb 1, 2010
For R17, is there any browser side technology can support COMET? Does JavaScript XMLHttpRequest can handle asynchronously chunk by chunk in response body? When I run the chat demo in Apache HTPP Server, the browser (IE & FireFox) always display all conversation after connection closed, instead of one by one right after I input.
Posted: Mar 3, 2010
What Content-Type will be used in R17 COMET events http response? multipart/x-mixed-replace or something else?
Posted: Mar 12, 2010
