I'm looking at it now for the same reasons. Actually, I've been looking at it for about six months, carrying it around in my briefcase, reading bits and pieces of it when I can... it is one of the most well-travelled pieces of documentation I own, having logged a few thousand air miles across three time zones. I think it and Sean's coding standards document have struck up a friendship, they've been in there so long.
The only thing so far has to do with his recommendation of adding a ColdFusion mapping for /com but even that is only an issue due to his recommendation that you map it to /WEB-INF/cfcomponents/com. I seem to remember there being a bug with CF mappings into the WEB-INF directory not working properly. Everything else looks to be excellent.
However, many people will also tell you that you should choose your architecture independently for each project. They may be right, but I'll be really happy if I can just get my team to adopt a standard architecture and methodology in the first place.
----------
The Other Eric
----------
No matter what stage of completion one reaches in a project, the cost of the remainder of the project remains constant.
-- Q's Law
| "Davis, Eric" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 03/24/2003 01:55 PM
|
To: [EMAIL PROTECTED] cc: Subject: [CFCDev] MVCF at benorama.com |
Link: <http://www.benorama.com/coldfusion/>
Word ver.: <http://www.benorama.com/coldfusion/patterns/MVCF.doc>
Has anyone looked really hard at this one? What are everybody's thoughts on this?
I'm looking for a replacement to Fusebox 3 for MX - FBMX is too slow coming, and probably won't make much sense anyway (I'm guessing it'll be quite obfuscatory and rather difficult to implement the first five to ten times).
He's put together quite a presentation, and he about has me convinced, if only I can simplify the structure a bit. I'm trying to find the right methodology for my team here to use, and they're NONE of them big methodology-users.
Anyway, just haven't seen any threads about this, and wondered if you folks had anything to say on the subject.
Which of course you must; you always do. ;)
Thanks,
ecd.
--
Eric C. Davis
Programmer/Analyst I
Georgia Department of Transportation
Office of I.T. Applications
404.463.2860.158
[EMAIL PROTECTED]
