We have written an ftp component organised around three ProviderEndpoints:
FTPGet, FTPPut and FTPDir. All accept an xml message like
<ftp>
<request>
<url>...</url>
</request>
</ftp>
FTPGet fetches the file specified in url, FTPPut uploads to the url (both
via
a marshaler), and FTPDir returns xml with a directory listing of url. We did
this to overcome these (perceived) limitations of servicemix's ftp
components:
1) FTPEndpoint's uri is immutable (or better, can't be taken from the
message)
2) There is no way to just find out what files exist on a remote site,
without
downloading them
3) FTPPollingEndpoint scales poorly because pollFileOrDirectory(...) does
not
distribute the load across nodes: the files are fetched locally and
sequentially
What we are currently doing to emulate pollFileOrDirectory is to build a
chain
FTPDir -> eip-splitter -> FTPGet
Does this make sense? Does this relate in any way to
http://www.nabble.com/listeners-in-container-and-MessageExchange-tf2815007s12049.html#a7862744
this message ?
--
View this message in context:
http://www.nabble.com/Some-comments-on-Ftp...Endpoint-tf2825900s12049.html#a7888193
Sent from the ServiceMix - User mailing list archive at Nabble.com.
