On Mon, 7 May 2001, Vincent Massol wrote:
> Instead of viewing the repository of jars as simply a set of files, I would
> prefer to view it as a set of services, all related to publishing and
> querying files. Examples of services would be :
> - get a version of a jar,
> - list all files released since such date,
> - upload a new version,
> - ...
>
> Or do you want to stay at the very low level of files and have the client
> side API implement these services by looking at a master index ? Ideally we
> would probably want that different types of clients can access these
> services.
>
> For example :
> - the jakarta web site itself could access these services for the news page
> and for the download pages
> - some external news portal could access these services to get information
> about latest releases of Jakarta
> - ...
>
> What do you want it to be ? Files or Services ?
Both :-) And a browser interface too! :-)
File-related services would be useful in automated build scripts.
Web-services based services would be useful in distributed repository
environments, as well as development tools that are repository-aware.
Browser interface would be a nice mechanism for the "Directory" portion of
commons that we have talked about, but never implemented yet.
> Thanks
> Vincent.
>
>
>
Craig
