That is actually intended exactly as written The XMPP method will work better behind firewalls, since the HTTP method requires a direct (unsolicited) connection from the event generator. XMPP allows the client to maintain an outbound connection to the XMPP server which can be used to return notifications.
> That is actually intended exactly as written The XMPP method will work
> better behind firewalls, since the HTTP method requires a direct
> (unsolicited) connection from the event generator. XMPP allows the client to
> maintain an outbound connection to the XMPP server which can be used to
> return notifications.
> Paul.
> On Thu, May 15, 2008 at 5:51 AM, Jud Valeski <j...@gnipcentral.com> wrote:
> > "For clients that may be behind firewalls, not have persistent names,
> > etc, the XMPP subscription method is far more likely to be
> > appropriate. "
> > -> "... etc, the HTTP subscription method is far more..."
On Thu, May 15, 2008 at 4:20 PM, Jud Valeski <j...@gnipcentral.com> wrote:
> hmm. that assumes the legwork to get an XMPP instance up and running > (punched through the firewall) has already been done; generally not > the case.
XMPP is a client-initiated protocol though - no holes need to be punched in the firewall. The protocol definition also includes mechanisms for HTTP tunnelling, so you can work behind HTTP/HTTPS-only proxies. Getting unsolicited web requests in would be substantially harder than getting an XMPP connection out.
