<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-2"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45"> <TITLE>RE: [JDEV] HTTP proxy</TITLE> </HEAD> <BODY> I think AIM supports HTTP polling now too. > -----Original Message----- > From: Ashvil [<A HREF="mailto:ashvil@i3connect.net">mailto:ashvil@i3connect.net</A>] > Sent: Tuesday, October 16, 2001 6:44 AM > To: jdev@jabber.org > Subject: Re: [JDEV] HTTP proxy > > > From: "Michal Leinweber" <M.Leinweber@sh.cvut.cz> > > Does anybody sucessfully used HTTP proxy in Jabber client ? > > I know 2 methods of using HTTP proxy for jabber client: > > > > 1) with method CONNECT - it works fine, but this method is > not commonly > used > > on all proxies and often disabled. > > 2) with method PUT using jabber server 1.4.1 buildin hack for this. > > We found this when building our IM client. > > The PUT method documented assumes a persistent connection. > Most HTTP Proxies > does not allow a persistent connection or block any request > responses after > the first. The method actually works if you can get a persistent HTTP > connection. > > MSN and Yahoo messengers support HTTP proxies and the way > they do this is by > polling every few seconds using a cookie or session request > identifier. Yes, > I know this is a horrible way, but try explaining that > end-users who are > behind an HTTP proxy. > > I don't know what the Jabber folks think of supporting this > kind of polling, > but they need to do this if they want to compete with MSN and Yahoo IM > systems. > > Regards, > Ashvil > > > > _______________________________________________ > jdev mailing list > jdev@jabber.org > <A HREF="http://mailman.jabber.org/listinfo/jdev" TARGET="_blank">http://mailman.jabber.org/listinfo/jdev</A> > </BODY> </HTML>