i think that including organization would a good idea for a couple of reasons. first, it would make it pretty clear that it's an URI is for an ASF jar. secondly, it would allow expansion later for non-ASF jars within the system. (even if they are hosted elsewhere.)
the project should simply include as much detail as it required to identify a unique releasable unit. so (for example) ant would be (something like) apache/ant whereas the commons logging api could be apache/jakarta-commons-logging-api (or something like that).
this idea also has the advantage of being much simpler :)
maybe the organization should be a domain name ie apache.org rather than apache.
- robert
On Saturday, March 1, 2003, at 06:56 PM, Nick Chalko wrote:
[EMAIL PROTECTED] wrote:
Nick,
can you explain why there is a need for a subproject and not a sub-subproject etc?
Good question.
This also releates to "what is a project" . Jakarta , avalon, turbine. poi, poi-contrib. On the one hand we could allow unlimited subprojects.
specify that projects must start with a letter, and version must start with a number.
Or the other aproach is only one level of projects then you have jakarta-avalon-fulcrum.
This is a namespace problem, how do we avoid naming collitions at Apache I suppose we could say that a "project"="cvs module" My preference would be for /project/[subproject/..]/version/artifact.
-- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au
-----Nick Chalko <[EMAIL PROTECTED]> wrote: -----
To: [email protected] From: Nick Chalko <[EMAIL PROTECTED]> Date: 03/01/2003 09:38AM Subject: ASF repository URI syntax
I think in general ./ or ./index.html should return a human readable form and ./index.xml should give machine readable form of the following
* / o list of projects in the repository * /project o list of subprojects o list of versions available if there is no subprojects * /project/[subproject]/ o list of versions available * /project/[subproject]/version/ o list of artifacts available. * /project/[subproject]/version/artifact. o downloads the actual artifact.
I think this a reasonable base set that support both a simple filesystem or an smart server.
These are just ideas to get the discussion of the protocol started.
Comments.
R, Nick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
