On 7/3/05, Mickael Remond <[EMAIL PROTECTED]> wrote: > J-EAI: integrating pubsub and Webdav for centralized file transfers: > http://www.3pblog.net/index.php?entry=entry050702-180443 > I am particularly interested in knowing how many of you would find it > interesting for IM and not EAI ?
I find it interesting. I think you'd have a case to make a JEP that supersedes JEP-0066: Out of Band Data. Your idea 1) uses pub/sub which will make Ralph happy, and 2) you have all of the back-end benefits of webdav, and 3) it can be perfectly described as a URL like OOB. The negatives IMHO: - YAFTP (yet-another-file-transfer-protocol) - Server requirements are higher (webdav) - Crap, google just told me that somebody thought of it already! :) http://www.xmpp.org/drafts/attic/draft-hildebrand-webdav-notify-00.txt http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/cvs/ietf/draft-hildebrand-webdav-notify-01.xml But this would be neat. There was someone on a mailing list recently who asked how he could restrict file transfers in his company. If you had a client which only supported a method like this, you could write policy around it which could be very benefiical for a corporate environment. -- Psi webmaster (http://psi-im.org) im:[EMAIL PROTECTED] http://halr9000.com _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
