Hi guys,
The Muc approach seems very interesting to us since we've based a lot
of our protocols extension on XEP-0045:
- mucom: multi user communities [1]
- mucol : multi user collaboration for which we have and audio/video
and appsharing implementation [2]
An easy way to allow all the occupants of a room to access a given
file might be to define the JID [EMAIL PROTECTED] (couldn't found a name
for that JID, is there any?) as an authorized entity. By such all room
jid ([EMAIL PROTECTED]/nick) would be authorized to download the file if
the users uses this JID in the HTTP request.
What is missing for us in the WebDav XEP is an additional layer that
would allow to manage files. For example, we might want to associate
files to a community, and allow members of this community to download
them. These files could be forms to fill in to join the community, ....
Basically, what we would need is XEP-0135 (file sharing) with XEP-0129
(WebDav file transfer). Is it possible to use Webdav as a stream
method for XEP-0096 (file transfer)?
Only thing missing then would be to allow users to add files to a MUC
room which shouldn't be too complicated.
What's great with XEP-0135 is that it'd work for MUC rooms and also
for users.
Gato is there any kind of WebDav support in Openfire?
Would jdisk allow such usage? If yes is there a way to see exactly
what's exchange between the server and the client (even if it's not a
XEP, just to look at the stanza workflow).
-Yann
[1] : http://www.xmpp.org/extensions/inbox/communities.html
[2] : http://www.xmpp.org/extensions/inbox/mucol.html
On 18 août 08, at 23:06, Zenon Kuder jr. wrote:
Hello,
Dne Monday 18 of August 2008 18:48:10 Peter Saint-Andre napsal(a):
http://dev.jabbim.cz/jdisk
Pavel and I have an action item to write up how this works. I think
you
use standard XEP-0096 to upload files to the server and it stores
them
for you, but I'm not sure how they are retrieved.
Jabber Disk works as a service/transport/bot. You register/add
contacts to
your roster which you can upload files to via ordinary filetransfer
(0096).
You can download them via commands - after typing the right command
the bot
initiates FT with you, which you accept and retrieve the file.
There's also
the possibility to have the files listed on http or build some other
service
upon that. (At Jabbim, we have http://album.jabbim.cz/ built upon
jabber
disk).
BTW, I've heard that Astro is working on ejabberd module version of
jabberdisk.
Gaston Dombiak wrote:
I didn’t assist to the Summit @ Brussels so I lack a lot of
information.
Having said that, What is JabberDisk? Can’t we use XEP-129 and may
be
also XEP-135 for that goal? We are using XEP-129 for file sharing
(in
rooms) and since it’s server based it should be possible to hook
up a
virus scanning solution. It is also possible to define users/
entities
allowed to get the file. So is JabberDisk == XEP-129? :)
-- Gato
On 8/18/08 2:20 AM, "Yann Biancheri" <[EMAIL PROTECTED]> wrote:
Hi everyone,
I remember we spoke about "JabberDisk" at the last XMPP Summit in
Brussels but I can't found any documentation on it in the xeps or
Jabber wiki. We'd like to share images between multiple xmpp
entities, and we have to check for viruses in the transfered file.
As
such, JabberDisk seems to be the way to go since it implies an
intermediate server. The File Sharing and File Repository and
Sharing xep
seems to be good starting points but I was wondering if the action
items
for Jabber Disk has been performed or not. We can help documenting
that
approach if nothing has been done yet.
--
Stop Skype Plague
XMPP Jabber ID: [EMAIL PROTECTED]
