Sounds good, as long as the store remains independent of them. I
don't want to get into the situation like in JIRA where you can't
rename a string key.
Before starting to hack on this, perhaps you could list out all the
keys you think are needed, and some examples? I'm interested in how
it relates to group IDs and artifact IDs in particular.
- Brett
On 22/12/2006, at 6:30 AM, Jesse McConnell wrote:
I am thinking about pulling a short term branch of continuum with
rahul and working on getting everything converted to using a string
based key project and project group reference in all apis and in all
of the UI decision making items. He has tomorrow off so I think that
unless anyone has any big issues with it we'll try and make that
branch and work on it tomorrow.
the end result of it would be:
* int id's for project and project group in the model are for internal
store usage
* name's for project and project group are for presentation
purposes only
* key's are for all api usage and passing around un URL's etc.
some quick benefits are:
* consistency across all apis and url manipulations
* ability to add quick url rewriting for direct linking of projects
foo.org/Doxia/Core
* common keys across running continuum instances for clustering
jesse
--
jesse mcconnell
[EMAIL PROTECTED]
