[sip-comm-dev] GSoC FileTransfer project


#1

Hey developers!

We are getting to the end of the GSoC project. During this project, I have
developed the file transfer for Sip-Communicator. It was a very interesting
project with a lot of various aspects. I have learned a lot, I think I also
have improved my skill and my English (a little bit).

The project is not yet completed, but the major part is already done. Most
of troubles come from Open source libraries which do not provide all methods
to transfer in p2p mode (yahoo), or which aren't compatible with some server
(jabber),... It will be necessary to often check updates of these libraries.

The GUI of the file transfer could also be improved (see screenshots). If
you want more information about the project, please read the next steps
manual.

I have written a manual of the next steps (see attached) in order to another
developer could be able to continue easily my work. *I also hope I can keep
my repository *in order to work on the project when I'll have time.

I would like to thanks my mentor Ulrich who has taught me lot of things,
Emil and Yana who were also very present and all Sip-Communicator
developers!

*I would like to know what files I have to send to you?*

*Must I to create a patch? Must I to create only one patch for the whole
project or must I to split it? If I have to split it, what are the criteria
(one patch per directory, one patch per protocol, ...)? *

*And to finish, when I create a patch, a new window opens, what I have to
choose? "From" I select the head of my project. "To", I select the head of
the trunk. Am I right?*

Best regards,

File Transfer Project Next steps manual.docx (223 KB)

···

--
Anthony Schmitt


#2

Hello Anthony,

Hey developers!

We are getting to the end of the GSoC project. During this project, I have
developed the file transfer for SIP Communicator. It was a very interesting
project with a lot of various aspects. I have learned a lot, I think I also
have improved my skill and my English (a little bit).

Glad you enjoyed it! We also loved having you and all the other GSoC
students working with us.

The project is not yet completed, but the major part is already done. Most
of troubles come from Open source libraries which do not provide all methods
to transfer in p2p mode (yahoo), or which aren't compatible with some server
(jabber),... It will be necessary to often check updates of these libraries.

That's curious. Do you mind telling us a bit more on your jabber problems?

I would like to thanks my mentor Ulrich who has taught me lot of things,
Emil and Yana who were also very present and all Sip-Communicator
developers!

You are most welcome!

Must I to create a patch? Must I to create only one patch for the whole
project or must I to split it? If I have to split it, what are the criteria
(one patch per directory, one patch per protocol, ...)?

RIght now the best thing you could do is keep your branch synced with
trunk. We already have a few patches waiting on this list so it is
probably going to take us a while before we handle them and all the
other gsoc projects. We will though!

Then, once we start working on it, we'll probably have questions and
suggestions, so it would help a lot if you were there to help us with
the improvements.

Cheers
Emil

···

On Thu, Aug 21, 2008 at 1:15 AM, Anthony Schmitt <anthony.schmittt@gmail.com> wrote:


#3

Hi fellow GSoCer,

···

On Thu, Aug 21, 2008 at 12:15 AM, Anthony Schmitt <anthony.schmittt@gmail.com> wrote:

I have written a manual of the next steps (see attached) in order to another
developer could be able to continue easily my work.

Could you make it available in the RTF or OpenDocument format please?

Cheers,

--
Sébastien Mazy


#4

About the Jabber problem, when I try to send a file with the smack library (
http://www.igniterealtime.org/builds/smack/docs/latest/documentation/extensions/filetransfer.html),
I first have used these functions:

manager = new FileTransferManager(jabberProvider.getConnection());

          // Create the outgoing file transfer
OutgoingFileTransfer transfer =
manager.createOutgoingFileTransfer(contact.getAddress());

But, an Exception was thrown and somthings about the fully jabber qualified
name was displayed. After some research, the fully qualified name of is
composed of *contactname@servername/ressource*. Then I have tried:

OutgoingFileTransfer transfer =
manager.createOutgoingFileTransfer(contact.getAddress() + "/Psi"); //because
I use Psi

or

OutgoingFileTransfer transfer =
manager.createOutgoingFileTransfer(contact.getAddress() + "/sip-comm");

but without any success. Only the Exception disapeared and nothing else
happened. The file was transfered. You can also see this thread:
http://www.igniterealtime.org/community/message/162326. I also have tried to
install a Jabber server (OpenFire from Ignite Realtime), maybe the server
was mis-configured, but I don't have succeeded to send a file. Maybe it
doesn't work because I have tried to send and receive the file on the same
computer (with Sip-Communicator and Psi)... If someone has any idea?

Other ressource: http://yvozin.free.fr/jabber/architecture.html#ch-11 about
the Jabber ID (in French).

Cheers,

File Transfer Project Next steps manual.rtf (5.78 MB)

File Transfer Project Next steps manual.pdf (500 KB)

···

2008/8/21 Sébastien Mazy <sebastien.mazy@insa-lyon.fr>

Hi fellow GSoCer,

On Thu, Aug 21, 2008 at 12:15 AM, Anthony Schmitt > <anthony.schmittt@gmail.com> wrote:
> I have written a manual of the next steps (see attached) in order to
another
> developer could be able to continue easily my work.

Could you make it available in the RTF or OpenDocument format please?

Cheers,

--
Sébastien Mazy

--
Anthony Schmitt