Craig R. McClanahan wrote:
> 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! :-)
I agree with Craig, but I want to crawl before I walk ;-)
Files come first, then services are based off of them.
>
> File-related services would be useful in automated build scripts.
File-related services will be the basis of any other service. But
really, it is not even a file, but an XML chunk sitting at a particular
URL, correct? Then the back-end doesn't matter, and neither does the
client. Want to use the RDBMS for the back-end? Go for it. Want a
client that uses the Properties Class? That's fine too.
>
> 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.
Based upon the XML repository, I was planning on creating an HTML-based
'human-readable' repository. That is easy enough once the information
is gathered into the repository DTD.
So, in conclusion my take is files first, then anything else that might
be useful and someone is willing to code up and support. I will be
creating the HTML version from the XML version as a static resource for
human consumption.
Scott
