[EMAIL PROTECTED] wrote:
Downfalls I've found with this approach though is it can be confusing to the naked eye, in that if you extend a class and you see this method "DispatchEvent(type,target)" and you can't see it in your API (because at runtime it was mixed in) you sit there going "WTF ..were the hell did that method come into play).. That or if they are nice coders and put a "dispatchEvent - with a note: This will be overriden by xyzobject" it may save some confusion but you still find yourself hunting around directories for source code :)
Just avoid inheritance (extends) or at least use sparingly - on the server side you don't need it as much as you do on the client side.
BTW, my ROT for inheritance is similar to primary keys - if the classification has anything to do with a real-world classification (e.g. mammals as opposed to UI Object) be very cautious.
What I meant by "sceptic in cfmx events" is that we are really hand-coding each workflow for an "even" type manually in that CFMX itself doesn't have any built-in events .. Which is fine I mean its getting down to "whats an event" is it really just a politically corect wording for when methodA triggers methodB,C,D,F or does it have a deeper meaning?.
No deeper meaning. And about Santa Claus...
Point is I felt a bit weird suddenly adding I guess "state" to CFMX when its typically not had it? Or did I mess that up further..probably the later on that one hehehe..
CF has always had one event - HTTP request. This is about using the same strategies you use for handling an HTTP request (have a scope to stick things in, have filters to handle the event (e.g. onRequestEnd), not caring where the request came from, just handling it) through the rest of your application.
Scott Out.
(Discussions like this is why I joined CFAUSSIE btw.. In hope of more like it hehehE)
P.S
Likewise, but I really have to dissapear now, looming deadline...
Robin http://www.rocketboots.com.au
--- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
