Le 2013-02-14 à 09:13, Musall Maik <[email protected]> a écrit :
> > Am 14.02.2013 um 15:09 schrieb Ken Anderson <[email protected]>: >> >> While a rule engine may seem like overkill, it really isn't. If you have >> just 2 discount schemes that could possibly overlap, you already could use a >> rule engine. In the rule engine, it will be real easy to add new rules as >> you add new discounts, that make sure you can't apply 2 discounts that are >> not allowed to be available concurrently. > > > Still I think for an app that sells WOWODC tickets, it's overkill. You can do > the rule engine yourself in one page of Java code. Or two, if you care to > write javadoc ;-) Well, yes, it's for the WOCommunity Store, so WOWODC tickets, membership and anything else we might sell (books, the USB stick, etc.) in the future. What I wrote in the past is using properties that defines the discount for conference items and using conditions on quantity to find which one to apply. But it's a bit more complex now, because of the membership. About the rules engine, even if it's overkill, I went to a business analyst course in the last couple of weeks and it would be a good practice to apply what I learned. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
