Hi,

I am newly subscribed to the user list. I am planning to embed the FTP
server with the Fabric3 (fabric3.codehaus.org) SCA container. SCA is a
standard that provides a programming and assembly model for building
SOA applications. One aspect of SCA is the ability to expose services
offered by components over remote transport bindings like HTTP-WS, JMS
etc.

I have been thinking about exposing services over FTP bindings. The
usecase to start with is to support an embedded FTP server within our
container, which would accept put requests from the end clients. The
container will have services registsred against directory paths to
which the users upload files. The idea is files are never materialized
on the file system, rather the container will map the path to a
service and stream the upload request directly to the target service.
The target services are provided by the users of the SCA container and
it is up to them what they do with the incoming data.

Now to my questions ;)

1. Is the above usecase realizable through the MINA FTP server?
2. In the implementation of the STOR command is the incoming data
always committed to the file system, if yes can we override this
behaviour?
3. I have been thinking os using the FTPLet API to get the
notification. I gather it is shared between multiple connections. Is
that the right place for state maangement for maintaining and
resolving the map of current directory path for each connection, so
that upload requests can be routed to user services?
4. Finally, is there a planned mvn release in the imminent future?

Kind regards
Meeraj

Reply via email to