[JDEV] libjabber 'port' and licensing

Dave dave at dave.tj
Wed Jul 24 11:58:24 CDT 2002


I'd prefer to avoid HTTP polling if possible, due to the fact that there's
no secure Jabber over HTTP polling standard, ATM.  It's really a rather
ugly solution, anyway.

If they have a transparent proxy (i.e., forwarding all queries to remote
port 80s to the proxy, or forwarding all queries that look like HTTP
requests to the proxy) and it supports keepalive connections, you may
be in business anyway.  Either way, trying to telnet to a port 5222
somewhere and giving a non-HTTP-like initial data stream will reveal
whether or not general outgoing TCP connections are allowed.

 - Dave


Wing, Oliver wrote:
> 
> Dave,
> 
> > Try telnetting to port 80 on one of 'em, and see if that works.
> > If that doesn't work, they've blocked outgoing TCP connections
> > at least to port 80.
> 
> Just small point, but simply telneting to a port doesn't tell you whether
> you really have a connection to that machine. Many corps have
> port-forwarding on 80 into a Proxy, to save having to do client
> configuration. What you'd need to test is whether you can do anything other
> than an HTTP request on that port.
> 
> I personally don't see a problem in HTTP polling, nor feel it's that
> complicated to implement.
> 
> Regards,
> 
> --
> Oliver Wing
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 




More information about the JDev mailing list