Brian... that's a bit too oversimplified.
At the very least you need:
An init() method which includes <cfreturn this />
setters for your properties or arguments to your init() method
CFCs that are thread-safe as singletons
If you don't know what any one of those 3 things are are or how to
implement them, don't use ColdSpring until you do. Gross digital harm
may ensue. ;)
J
PS - Reactor is ColdSpring friendly from the get-go, so if that's all
you want to use it for go ahead. If you're going to use your own
CFCs, however, I strongly recommend you know what you're doing before
you crash a shared server or drive your sysadmins utterly bonkers
(and potentially really mess up your users). :D
------------------------------------------------
Jared C. Rypka-Hauer
Continuum Media Group LLC
http://www.web-relevant.com
On Jul 16, 2007, at 10:04 AM, Brian Kotek wrote:
ColdSpring doesn't really need anything for your CFCs to play well.
If you have CFCs you can use ColdSpring. Where your methods are or
where you think they should ideally go is a separate issue. ;-)
Internally, Reactor caches the following types of objects: Dao,
Gateway, Metadata, and Validator. So when you ask for any of these,
Reactor only creates them once, and then subsequent requests for a
specific one of these will return the cached instance.
Records are not cached. So when you ask for a Record object from
the factory, you will always get a new instance. So in your example
the answer is no. Each user has its own Record object with its own
data.
Also just FYI, Iterator objects are not cached either.
Hopefully that helps.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[EMAIL PROTECTED]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
