[JDEV] file transfer

[PINSON Frederique FTRD/DMI/LAN]

hi..

>for my file transfer i want to implement in my jabber client i need 
>some tags to manage the infomration exchange between both 
>clients.
>the information about the file (filesize, byte to 
>start at, filename, IP, port) should be transfered within an xml 
>message to the other client to manage a handshake...

Have you considered using WebDAV protocol for this ?? 
it should do the job for you and lot more... (lock files, versioning...,
though it is built on "http standard" :)

regards, 

Frédérique Pinson
Frédérique Pinson
FTR&D - DMI/GRI
tel: 33 2 96 05 30 85
fax: 33 2 96 05 32 86
 


-----Message d'origine-----
De : kmq at gmx.at [mailto:kmq at gmx.at]
Envoyé : mardi 12 février 2002 02:00
À : jdev at jabber.org
Objet : [JDEV] file transfer


hi
for my file transfer i want to implement in my jabber client i need 
some tags to manage the infomration exchange between both 
clients.
the filetransfer will be P2P and not the http "standart". I will not use 
the http standart because i want to be able to continue broken 
downloads and it must be possible to connect->sendfile as well as 
connect->getfile. (This would enable me to establish filetransfer 
even if one of the users is behind a firewall)

my filetransfer is a simple tcp connection that will get transfer the 
bytes of the file... the information about the file (filesize, byte to 
start at, filename, IP, port) should be transfered within an xml 
message to the other client to manage a handshake. Now my 
question: may i use the oob tag? all the samples have 
httü://12.12.12.12/file.zip or something in it... can i use my own 
tags in it? like 
<ip>12.12.12.12</ip><port>2344</port><filename>blah.zip</filena
me><filesize>12345</filesize>....
_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20020213/c98b07e2/attachment-0002.htm>