Looking at the repository block, one will see that there is already a RepositorySource, but that source and the RepositorySourceFactory are not meant to be used with the new Repository interface from Guido.
What I have in mind is:
A new RepositorySourceFactory should simply look up the appropriate respositroy via the RepositoryManager and pass that to RepsitorySource. The source than acts on the Repository interface to provide a sources functionality.
Does this make sense?
It does.
However please consider the Repository interface unstable (if not at "proposal stage", but definately not finished) and I currently wouldn't move too quick building further components on top of it.
If you need a Source for accessing WebDAV, why not use the WebDAVSource?
Guido
Guido?
On Thu, 2004-04-08 at 15:59, Rolf Kulemann wrote:
Hello,
I currently test and play around with the Repository block. I guess a RepositorySource would be useful at least for my personal needs.
I'm going do some coding on it and wonder what involved Cocooner's think about it.
Since it is possible to configure different "backends" being used through the repository interface it would make sense to me to access such a source like:
{repository:backend/path}
where backend is a name configured for a particular repository impl. i.e. - mywebdav as a name for webdav backend - myslide ........
Any ideas on this?
