On 2004-10-05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> 1. A purely orthogonal module
>>
>> Here, the helper module has no dependency or relation to
>> CGI::Application. Most other modules you might employ from CPAN would
>> fall into this category. For example, using CGI::Simple, SQL::Abstract
>> or Data::Grouper.
>>
>> In many ways, this is the ideal setup, because the lack of
>> interdependence reduces the overall complexity of your application.
>>
>> Unfortunately, writing this of module for a custom solution can tedious
>> if there /are/ a lot of interdependencies you want to consider, such as
>> sharing configuration data, a database handle, session information or
>> CGI query parameters.
>
> This is the way I write my applications.
Matthew,
It sounds like you have a very clean MVC paradigm that you've
standardized on. Do you have any specific coding tips to share
about to make that clean separation between the model and controller?
Do you use Class::DBI to manage the database integration?
For your model classes, how do you handle access to configuration
variables?
Has your workflow produced any kind of re-usable framework (beyond
CGI::Application), or is more of a philosophy in action?
As far as book recommendations go: One of my favorite has been "Code
Complete". It gave me new and valuable ways to think about how to
effectively structure code.
I don't think it's contains a line of Perl, but at this level of design,
it hardly matters.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
[EMAIL PROTECTED] Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
