Re: Application Development with PostgreSQL - Mailing list pgsql-novice

From:               Josh Berkus <josh@agliodbs.com>
Organization:       Aglio Database Solutions
To:                 Ron Johnson <ron.l.johnson@cox.net>,
    PgSQL Novice ML <pgsql-novice@postgresql.org>
Subject:            Re: [NOVICE] Application Development with PostgreSQL
Date sent:          Sun, 4 May 2003 20:37:03 -0700
While I do not claim to be an authority on these matters, I would have to agree with
Josh on this one, its almost trivial to set up a decent VPN these days. The question, as
always, is how much time you or your client want to spend on security and ergonomics.

A web app can host the application and provide a repository for any helper applications
that might be needed, (say a grid applet or whatever). The thin client that the browser
offers may not be ideal, but it is exteremely versatile and robust. You just have to weigh
the requirements and choose the right horse for the course.

What ie5/php/postgresql+a reliable network connection offers out of the box is
ridiculously good, and should make it a combination worth considering. (If you want tidy
reporting, grab the pdf library). I'm a big python fan, but building the client side from
scratch, maintaining  and distributing it is never simple. As for caching  look up lists, if
you gzip things, it shouldn't take any longer than downloading a gif.

The wonderful thing is that the thin client is not just here, it's everywhere. This leaves
the developer one less thing to worry about and allows them to concentrate on
correctness, and finally performance(which is always the straw man of computing
disagreements).
Thats my two bob's worth of opinion.
Cheers
Paul Butler
on,
>
> > And these are also important issues!
> >
> > Using Python/Perl/Java (am I missing one?) would mitigate platform
> > dependence.
>
> Yes.  But she was comparing rapid app dev kits, not programming languages;
> Delphi and VB are fast GUI-builders.
>
> > Wouldn't these (especially 3 & 5) be solved by Terminal Services.
> > #3 would also be partly (or totally, with some care) solved by having
> > the app residing on a network drive.
>
> Yes.   But if you're going to do that, why bother with client-side
> programming?  I suppose if your app needs advantages 1 & 2, I guess ...
>
> And applying app changes across sessions on a terminal server is still
> significantly more trouble than applying a change to a web app.  With a PHP
> app, you just save the new file in /wwwroot, and bang!  It's applied to all
> users.
>
> > > 6) Vastly more cumbersome external access for work-from-home users.
> >
> > How so?  I'd think that "traditional" C/S would be faster, because
> > certain "objects" can be intelligently cached by the client, on
> > start-up, for example.  Don't look-up lists have to be sent across
> > the wire every time on web pages?
>
> If you want home access to a client side app, you have to mess with VPNs and
> firewalls and/or remote terminal services.   Ever try providing support for
> 150 user with gods know what running on their home machines, along with more
> viruses than megabytes of ram?  (we had a fun conversation when the IT dept
> at one client got a phone call from a staff member who couldn't figure out
> how to install Mozilla.  Turns out the staffer had an Amiga)
>
> For a web app, you just route a path from the web server to the internet.
> Then tell the user to use a brower.   Very easy.
>
> From my perspective, the age of the "thin client" is here.
>
> --
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>