with apache and php and backend database you can create as much dynamic content as you wish. so why would you need to turn it into a web app? will it not limit its adaptability to future requirements?
From: Chris Stinemetz <chrisstinem...@gmail.com> To: Rajeev Prasad <rp.ne...@yahoo.com> Cc: Perl Beginners <beginners@perl.org> Sent: Friday, September 16, 2011 11:55 PM Subject: Re: website vs web app On Fri, Sep 16, 2011 at 6:10 PM, Rajeev Prasad <rp.ne...@yahoo.com> wrote: > why do i need a web app? becuase of size of my project? I mean if it is going > to be a very big website with lot of pages and tables etc. should i have a > webapp? > > apache and cgi wont cut it? (alongwith other technologies used commonly in > websites) I think it depends what you are looking for. I tend to believe you can have either static pages or dynamic pages. Dynamic meaning: communicating with a database while making the user experience more interactive instead of your typical static pages. I can think of several reasons for a web app and it isn't because of the size of a website, but instead how dynamic you want it to be. I don't have much experience with cgi but I do with apache and php. I am now also trying to learn catalyst since I prefer perl over php.
