Additionally, events are only thrown in resources currently. (IIRC)
Kind of a tough one, we don't have clear lines drawn.
I think the initial plan was curator = business logic and database
access all in one.
I really don't know if we should do:
- resource = pure rest layer, new middle layer = business logic,
curator = db access.
- resource = pure rest layer, curator = business logic + db access
- resource = business logic, curator = db access
On Tue, Jun 29, 2010 at 10:30 AM, Bryan Kearney <bkearney(a)redhat.com> wrote:
I have had question about how fat resources should be. I am going
to
pick on Ajay (sorry) because I was looking at his patch for the
LIFO/FIFO Stuff (good job).
In his patch [1] he has added the revocation code into the Owner
Resource. Should this actually be in the curator level? There are other
example of this (ConsumerResrouce.create adds the identity certificate)
as well.
My main question is, should the resource be "only" going from REST to
internal API? Or should there be business logic there?
-- bk
[1]
http://git.fedorahosted.org/git/?p=candlepin.git;a=commitdiff;h=9898dccdb...
_______________________________________________
candlepin mailing list
candlepin(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/candlepin
--
Devan Goodwin <dgoodwin(a)rm-rf.ca>
http://rm-rf.ca