Re^2: Web design and Perl/CGI business logic programming

dHarry, thanks for such usefull comments. Could you clarify please, what you mean by
/*First of all web clients are supposed to be * thin * clients. Although you can beef things up they will never match a * fat/rich * client developed in C++/VB/... etc.*/
Does it mean that with Perl/CGI I cannot do things which are possible with C++/VB/... ?
and
/*A web client should be a thin client.*/

Comment on Re^2: Web design and Perl/CGI business logic programming

Replies are listed 'Best First'.
Re^3: Web design and Perl/CGI business logic programming by dHarry (Abbot) on Aug 23, 2008 at 14:12 UTC
I agree with Your Mother (what a name) below, “never” is a bit long. With fat- or rich clients I mean for example a C++/Visual Basic application. You can create great GUI’s in it and you compile it into an executable that resides on the client (in general, there are other architectures possible). With the thin client most of the processing is done on the server side, for example the web server. The server processes the user input and returns html to the clients’ browser (again in general and simplified). So the only thing a client needs is a web browser. You can enrich a thin client to behave like a fat client so you can use Perl/CGI to make flashy applications. Keep in mind that it takes effort though. How big is your application? How many screens do you foresee? How complex is the User Interface logic? Are you proficient in JavaScript/CSS? Frameworks based on MVC definitely have a learning curve (I am with Your Mother again). If your application is simple, not too big, it might be overkill, like trying to shoot a mosquito with a canon. That’s why I said you need a certain “critical mass” before you go MVC. Cheers, dHarry	[reply]

Replies are listed 'Best First'.

Re^3: Web design and Perl/CGI business logic programming
by dHarry (Abbot) on Aug 23, 2008 at 14:12 UTC

I agree with Your Mother (what a name) below, “never” is a bit long.

With fat- or rich clients I mean for example a C++/Visual Basic application. You can create great GUI’s in it and you compile it into an executable that resides on the client (in general, there are other architectures possible).

With the thin client most of the processing is done on the server side, for example the web server. The server processes the user input and returns html to the clients’ browser (again in general and simplified). So the only thing a client needs is a web browser.

You can enrich a thin client to behave like a fat client so you can use Perl/CGI to make flashy applications. Keep in mind that it takes effort though. How big is your application? How many screens do you foresee? How complex is the User Interface logic? Are you proficient in JavaScript/CSS?

Frameworks based on MVC definitely have a learning curve (I am with Your Mother again). If your application is simple, not too big, it might be overkill, like trying to shoot a mosquito with a canon. That’s why I said you need a certain “critical mass” before you go MVC.

Cheers,
dHarry

[reply]