Обсуждение: Java vs. PHP (was web interface for postgreSQL-P.S.)

--- Jason Davis <jdavis@tassie.net.au> wrote:
> any time. It is very similar in principle to PHP, being a server-side
> scripting language CGI on a UNIX box, with the code embedded into HTML
> pages,

I was wondering what sort of impact PHP (and I suppose this heitml) had
on the server.  It seems that it is pushing the calculations to the
server, where Java and JavaScript are executed on the browser.



=====
Wayne Johnson,             | There are two kinds of people: Those
3943 Penn Ave. N.          | who say to God, "Thy will be done,"
Minneapolis, MN 55412-1908 | and those to whom God says, "All right,
(612) 522-7003             | then,  have it your way." --C.S. Lewis

__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/

On Wed, Dec 20, 2000 at 10:36:31AM -0800, Wayne Johnson wrote:
>
> I was wondering what sort of impact PHP (and I suppose this heitml) had
> on the server.  It seems that it is pushing the calculations to the
> server, where Java and JavaScript are executed on the browser.
>

Most web / database work in Java is server-side Java. The only kind
of Java that gets executed in a browser are Applets, which have largely
fallen into (well-deserved) disuse. Servlets and Java Sever Pages (along
with JDBC) are the mainstay Java technologies for web / database
interfaces.

However, just because a technology is server-side does not mean it
will have an adverse performance impact on the database. Your web server
can and usually does live on a different machine than your webserver;
your dynamic page-generation tool is a client to the database. This
architecture performs a lot better than an alternative where
hundreds of clients might potentially maintain open connections to
the database, as would be the case if you let browser-resident
Applets directly connect to the db.

     Steve