For this type of thing, I would put it in one chunk of code. Form and all. Easier to manage that way. Of course that's me. Let's see some of the code.
-----Original Message----- From: "Eric Sun"<[EMAIL PROTECTED]> To: "Perl-Win32-Web Mailing List"<[EMAIL PROTECTED]> Date: Wed Dec 12 08:36:15 PST 2001 Subject: (no subject) >Experts, >We have a design question. >We are writing a web page to allow our registered clients to log on our web >site to do their customized database search. > >First, a welcome page for authentication, that's a form to submit(cookie is >set after). >Second, clients logged on, config their search setting(cookies is set also). >Last, clients have a bunch of menu to choose to do various analysis based on >our database. > >QUESTION: Should we use one perl file to implement all analysis or use >separate files for each of them? I worry about the size of the single file, >too big to manage. > >Thank you for your thoughts, > >Eric > >_______________________________________________ >Perl-Win32-Web mailing list >[EMAIL PROTECTED] >http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web ___________________________________________________ GO.com Mail Get Your Free, Private E-mail at http://mail.go.com _______________________________________________ Perl-Win32-Web mailing list [EMAIL PROTECTED] http://listserv.ActiveState.com/mailman/listinfo/perl-win32-web
