> > > time promoting it. Nevertheless here are some things to
> > > consider when choosing your framework.
> > > -- the single biggest problem with building a Web
> > > application is actor messages. It is not CF code, nor DB
> > > design, nor Web page layout, nor networks, nor performance.
> >
> > Without commenting on the usefulness of switch-box, which
> > I'm not qualified to do, I would disagree with your
> > characterization of "the single biggest problem" with web
> > applications. In my experience, as one who has reviewed
> > hundreds of problematic web applications, the "single biggest"
> > problem is all things database-related: database schema design,
> > inefficient database access, insufficient caching of database
> > records (and other generated output for that matter). Admittedly,
> > I'm stretching to classify this as a single problem, but there
> > it is.
>
> Yes. Good database design and efficient application interface
> is essential to a well functioning Web application that uses
> a database. There are thousands of techniques available to
> make great application.
While there may be thousands of techniques available to make great
applications, that is neither here nor there. My point, to the extent to
which I have one, is simply that the most common failings in web
applications that I've seen are all database-related, rather than anything
to do with actor messages. You're free to disagree, of course.
> Perhaps your experience relates to applications that did not
> tap into those techniques.
Yes, to the extent that I'm often asked to review applications that aren't
adequate for their task, those applications don't tap into those techniques.
Of course, at that stage the client typically doesn't care too much about
whether they're using OO or procedural concepts for their applications -
they simply want them to work.
> In your reviews, what techniques and tools do you use to
> analyze and manage actor messages?
Given that most CF applications tend to be written in a procedural manner,
rather than an OO manner, this has not typically been an issue. Most of my
clients don't want me to pick a language or programming paradigm for them -
they simply want things to work as well as possible within the existing
model they're using. In addition, it's worth pointing out that you can write
perfectly suitable web applications using only procedural languages and
concepts, in which case you could go your whole life without knowing or
caring about actor messages. Finally, I'm not convinced that it makes sense
to apply OO precepts so thoroughly to CF - if you really want to write OO
code, why not use an OO language?
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
