It is a database driven collaboration application. Function such as "calendar", "tasking" etc. (mysql is the database enginee)
These types of applications are already publicly available in Perl. Siesta (Mailing List), Bricolage (uses PgSQL) for site CM, reefknot.sourceforge.net/ for RFC 2445 Calendaring...
Maybe you should "spill the beans" about your complete application and prevailing needs and see if there isnt already a open source path -- why beat yourself to death with propritary code -- even if that code is Perl.
I have no ideal why it was writtn without calling any pre-built library. Perhaps, performance was the primary
That is no longer a valid excuse -- the CPAN modules in many respects are "just as fast" as most hand written code. In many instances better because of what you state below with regard to maintenance.
concern. Yet, It is becoming a big maintance issue and
I am convinced it is not worthwhile.
Try to image: The program compose each page byte by
byte such as the HTML form. It is very hard to make
any change without trying a few iteration.
So far, I probably would rate the "debuging capability
as the top consideration.
The debugging issue I dont know about -- I am not sure what detailed debugging system exists for anything other than Template Toolkit. After all you can use Perl to debug itself using the Perl Debugger.
http://www.template-toolkit.org/
HTH/Bill
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
