> I recently did a lot of refactor in Camel 2.0 on the ftp/sftp
> component towards a goal of a VFS in Camel itself.
> So there code be shared code between file and ftp component.
>
> What basically needs to be done to add a potential new file based
> component is (based on the ftp refactoring).
>
> 1) Implement transport specific consumer (see FtpConsumer,
> SftpConsumer, and FileConsumer)
> 2) Implement transport specific operations (see FtpOperations,
> SFTPOperations)
>
> That's it. Well if you added a new transport to camel-ftp that is. But
> this could pave the way for the Camel VFS, where we basically needs to
> refactor the file component to implement a FileOperations as well.
> Then they could all share the same producer.
>
>
Would you suggest moving the various (new) interfaces up to camel-core where
camel-file is, and then having a camel-ftp and camel-vfs ?
camel-core{contains camel-file}
camel-ftp
camel-vfs
or
camel-file
camel-ftp
camel-vfs ?
