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 ?
Sorry - was a touch hasty with the return key.
I want it to be both :
Files, because you might want to have a local repository for your
application and development use.
Having running services is also a good target to shoot for - but places
a larger burden on the repository site(s).
So I figured we should put a question like this off for a little while,
until we have a change to play with and evolve whatever we decide to
use. I think actual use will give us hints how to proceed.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
"still climbing up to the shoulders..."
