216
edits
Difference between revisions of "Psi JFT"
Jump to navigation
Jump to search
m
no edit summary
Neustradamus (talk | contribs) m |
Neustradamus (talk | contribs) m |
||
| Line 28: | Line 28: | ||
'''Synopsis''' | '''Synopsis''' | ||
The objective of this project is to help the Jabber team in finishing a | The objective of this project is to help the Jabber team in finishing a XEP that defines a media description format for Jingle File Transfer sessions and, as soon as this XEP is released, write a module that implements this functionality for the Psi client. | ||
As the manner of establishing p2p connections is one of the main reasons for Jingle's success, having a File Transfer system based in it would have a much better result in comparison with the methods used nowadays. | As the manner of establishing p2p connections is one of the main reasons for Jingle's success, having a File Transfer system based in it would have a much better result in comparison with the methods used nowadays. | ||
| Line 46: | Line 46: | ||
'''Deliverables:''' | '''Deliverables:''' | ||
* A | * A XEP that defines a media description format for Jingle File Transfer sessions; | ||
* A module implementing the Jingle File Transfer functionality for Psi; | * A module implementing the Jingle File Transfer functionality for Psi; | ||
| Line 59: | Line 59: | ||
With Jingle offering a standard for initiating and managing peer-to-peer sessions, in order to serve as a base for all bytestream-based services, nothing more logical than using it to define File Transfers in the same way that is being done with Audio and Video, making it easier to implement by other clients. | With Jingle offering a standard for initiating and managing peer-to-peer sessions, in order to serve as a base for all bytestream-based services, nothing more logical than using it to define File Transfers in the same way that is being done with Audio and Video, making it easier to implement by other clients. | ||
The | The XEP that defines this has already been started by the Jabber team, so I would be working with them to help finish it (with a prototype implementation to help with testing) and afterwards implement a reference module for Psi. | ||
My motivation for this project is quite strong : I'm behind a NAT/Firewall and I can't make efficient file transfers on any IM clients, so I would be really glad to solve this problem. | My motivation for this project is quite strong : I'm behind a NAT/Firewall and I can't make efficient file transfers on any IM clients, so I would be really glad to solve this problem. | ||
| Line 73: | Line 73: | ||
- 0.0.1 - Work in the protocol: | - 0.0.1 - Work in the protocol: | ||
- Start working at the protocol definition with the responsible group at Jabber; | - Start working at the protocol definition with the responsible group at Jabber; | ||
- Implement a prototype to help with the validation of the | - Implement a prototype to help with the validation of the XEP; | ||
- 0.0.2 - Implement the Protocol: | - 0.0.2 - Implement the Protocol: | ||
(As soon as the | (As soon as the XEP concerning to the Jingle File Transfer is released) | ||
- Start the definitive implementation using Psi; | - Start the definitive implementation using Psi; | ||
| Line 100: | Line 100: | ||
[http://xmpp.org/extensions/xep-0166.html XEP-0166: Jingle] | [http://xmpp.org/extensions/xep-0166.html XEP-0166: Jingle] | ||
[http://code.google.com/apis/talk/libjingle/ | [http://code.google.com/apis/talk/libjingle/ libjingle] | ||
[http://ejabberd.jabber.ru/ ejabberd] | [http://ejabberd.jabber.ru/ ejabberd] | ||