Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Communications Framework (ECF) » Provider for ISendFileTransferContainerAdapter
Provider for ISendFileTransferContainerAdapter [message #624671] Fri, 02 January 2009 17:55 Go to next message
Florian Hackenberger is currently offline Florian HackenbergerFriend
Messages: 123
Registered: July 2009
Senior Member
Hi!

According to [1], there are currently four providers for the api:
- URL/URLConnection Protocols (file retrieval)
- Apache Httpclient for HTTP/HTTPS
- BitTorrent (file retrieval)
- XMPP (peer-to-peer file sending)

According to the comments in brackets, URL and BitTorrent are for retrieval
only, and stemming from the name, Httpclient seems to provide file
retrieval only too. That leaves me with XMPP for peer to peer file sending.
Is that really the only option? A simple TCP based provider should be quite
easy to implement, shouldn't it? Can somone please provide me some hints
where to start or point me to a simple peer-to-peer implementation which
does not require an external server?

Cheers,
Florian

[1]
http://wiki.eclipse.org/ECF_Providers#File_Transfer_.28org.e clipse.ecf.filetransfer.29

--
DI Florian Hackenberger
florian@hackenberger.at
www.hackenberger.at
Re: Provider for ISendFileTransferContainerAdapter [message #624672 is a reply to message #624671] Fri, 02 January 2009 18:22 Go to previous message
Scott Lewis is currently offline Scott LewisFriend
Messages: 975
Registered: July 2009
Senior Member
Hi Florian,

DI Florian Hackenberger wrote:
> Hi!
>
> According to [1], there are currently four providers for the api:
> - URL/URLConnection Protocols (file retrieval)
> - Apache Httpclient for HTTP/HTTPS
> - BitTorrent (file retrieval)
> - XMPP (peer-to-peer file sending)
>
> According to the comments in brackets, URL and BitTorrent are for retrieval
> only, and stemming from the name, Httpclient seems to provide file
> retrieval only too. That leaves me with XMPP for peer to peer file sending.
> Is that really the only option?

No, the documentation is a little out of date. There are two others
available:

1) SCP/SSH. This is available via the org.eclipse.ecf.provider.scp plugin.

2) Eclipse File System...aka EFS. What we've done here is implement the
ECF async file transfer API using EFS itself...meaning that any EFS
provider can also serve as an ECF filetransfer implementation. There
are several EFS implementations out there...e.g. Webdav, FTP, others (I
think). I believe the DSDP project has several impls, for example.

And so these can/could also be used via
org.eclipse.ecf.provider.filetransfer.efs. Note the URL format in this
case is:

efs:<uri> e.g. efs:ftp://foo.bar/baz.txt (for the EFS ftp provider).

>A simple TCP based provider should be quite
> easy to implement, shouldn't it?

Yes. In fact, one can use
org.eclipse.ecf.provider.filetransfer.outgoing.AbstractOutgo ingFileTransfer
to help with this implementation if desired (in
org.eclipse.ecf.provider.filetransfer).


Can somone please provide me some hints
> where to start or point me to a simple peer-to-peer implementation which
> does not require an external server?

Although this is not what you are looking for, note that the jetty http
server (and OSGI http service) are both built into Equinox and
distributed with Eclipse...so it can be used to serve materials as well.

But currently XMPP is the only impl that doesn't require an 'external'
server.

Note that one thing that we can/could easily do is to implement the ECF
filetransfer API using (e.g.) the datashare API. This would then allow
any provider for the datashare API to send/receive file transfers. We
just haven't done this as yet.

Thanks,

Scott
Previous Topic:ECF Twitter Connection Error
Next Topic:file sharing in ECF
Goto Forum:
  


Current Time: Fri Dec 19 06:48:57 GMT 2014

Powered by FUDForum. Page generated in 0.03889 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software