HTTP has very good support for old and/or watered-down clients and servers, because that's a problem that HTTP has had to deal with for more than a decade now. PDAs would probably implement _very_ minimal HTTP clients/servers, while large filesharing hubs could employ a full-blown server like Apache, possibly even allowing HTTPS connections, etc. Another neat payoff is that the Jabber clients can stay a lot simpler and be mostly independent of the file transfer components, if desired.
- Dave Richard Dobson wrote: > > > > And this will work with existing Jabber clients. > > Also on this point just because thats the way it was done by previous people > it does not mean we should just retrict ourselves to HTTP, it may not be > compatible with these until they were updated but the whole point of this > discussion is to end up with a proper standard file transfer protocol that > can be deployed to all clients and I still think the HTTP protocol is > unnecessary and bloated especailly once you get down to small clients and > PDA's etc where every k counts. > > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
