Philippe Raxhon wrote: > Just some thoughts. > > It could be time for the jabber community to define an "official" way > file sharing should be done. I don't say here that it should be > written by jabber folks, or that it should be part of the jabber > server, but having a implementation reference could help. For > instance, using webdav is a very good idea, but, if this solution is > choosen, it should be said somewhere that's the way jabber clients and > transports should/could do file sharing. But more than that, an > implementation of webdav (webdav is only a protocol after all) could > become the, once again, "official" file sharing solution,
Sure, our official mechanism is via HTTP through jabber:iq:oob. WebDAV is considered a proxying mechanism (because you cannot connect to a fake web server run by clients behind a corporate/private firewall or nat). There was also a mechanism called PASS written up in an experimental JEP a while back (basically as an alternative to WebDAV/jabber:iq:oob which allows for better proxy negotiation and for data to be streamed rather than store/forward), but it appears to be dead/sleeping. -David Waite _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
