On 09/17/2010 01:38 PM, Devan Goodwin wrote:
Design here:
https://fedorahosted.org/candlepin/wiki/MultiOwnerUsers
This feels like it's not quite doing the problem justice but looking
through it it may not be as bad as I thought. Anything I missed? Other
thoughts / comments?
Cheers,
Devan
Sorry I'm going to use your design as an example :D
The 'design' seems to be a list of tasks. What I don't see is anything
describing the relationship between owners and users, what will the
data model look like?
What is the name of the HTTP header to be used? What is it used for?
I'd like to see #4 expanded, something along the lines of:
Candlepin will need to know if an authenticated user has access to
multiple users [did you mean owners?]. In order to accomplish this
check, we will use a [guice method | resteasy] interceptor to perform
this check ...
What are some of the use cases for having multiple owners? And how
does the implementation address those use cases?
jesus
--
jesus m. rodriguez | jesusr(a)redhat.com
principal software engineer | irc: zeus
red hat systems management | 919.754.4413 (w)
rhce # 805008586930012 | 919.623.0080 (c)
+---------------------------------------------+
| "Those who cannot remember the past |
| are condemned to repeat it." |
| -- George Santayana |
+---------------------------------------------+