I'd do it this way too. You can mix this with the UUID idea; you create the user with a new UUID, get it into the DB etc and then manage this user's newletters with the newsletter manager CFC. It means the newsletter info becomes a property of the user, which makes sense; users have newsletters and "have" is a giveaway that a property is the way to go.
On 2/11/06, Aaron Roberson <[EMAIL PROTECTED]> wrote: > Deanna Schneider wrote: > > Well, you could have some object aggregation. So, for example, the user CFC > > could have an instance of the newsletterManager cfc. So, if a new user is > > created, and they've requested access to certain newsletters, you'd just run > > the functions from within the user cfc. Or, if you instantiate a user as an > > object, there should be a "getId()" function that can be called once it's > > been instantiated. Then, use that id in a separate call to the newsletter > > cfc. > > I am learning Java at my local community college and I was thinking > that instantiating an object of the user.cfc might help avoid > potential race conditions, but this stuff, including what you have > mentioned, is a bit over my head. I would definately need some help > understanding all of this. -- CFAJAX docs and other useful articles: http://jr-holmes.coldfusionjournal.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232028 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
