The web pages use a combination of id's which are currently jpox id's and in some places the actual freeform name string is being passed around on the URL in order to influence program logic and security decisions..
all of that is what I want to unite behind stronger typed string keys. jesse On 12/21/06, Christian Edward Gruber <[EMAIL PROTECTED]> wrote:
Sounds great to me. But I'm confused. Are the api's passing around "keys" as in database keys (id), or so-called business keys, i.e. the project group's text id and the project's text id? I presume the latter, given the earlier discussions. Christian. 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 > -- *christian** gruber + process coach and architect* *Israfil Consulting Services Corporation* *email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*
-- jesse mcconnell [EMAIL PROTECTED]
