lnd@hnit.is wrote:
>It may be added to the Mark's points bellow that PHP has more libraries in
>the out of the box setup (like regular expressions) but PHP is interpreted
>(right?) while JSP is compiled: when I was making decision I have chosen JSP
>because of "compiled" criteria: I do like the idea to catch as many bugs as
>possible at compile time and rather hate "interpreted" development.
>
>
Sorry but your not correct.
Java is a binary 'interpreted' language. Although it is binary it is not
a binary exucutable
native on almost all platforms. The java executable interprets the java
binary code and
translates it into native machine executable code. Since the binary data
is tokenized it is
more efficient and has already had it syntax and scopes verified so less
processing is
required making it faster once it has been compiled.
One of the bigger advantages of JSP is the two way data flow capability.
With the
java application running at the client end providing the interface, and
the java servlet
running at the server end doing the I/O, JSP can make a more fluid
feeling interface.
With PHP once the page is rendered it is static.
I did not know that AOLserver was TCL based, but that is if I remember
correctly
simmilar to JSP, but I don't remember it being precompiled. I
experimented with
a tcl module and appletts years ago, but I didn't have an application
for it back then.
I do have a DB application that needs to be able to quickly "flip"
between a selection
records now. I have not decided which way to go yet.
>
>
>>In terms of installing and configuring, well PHP is just an Apache
>>module, so it is reasonably easy to get going.
>>
>>
>
>But once JSP starts running - it does run. One has to invest into this
>setup/configuration job once.
>
>
>Brgds, Laimis
>
>
>
>
>>-----Original Message-----
>>From: pgsql-general-owner@postgresql.org
>>[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Mark Kirkwood
>>Sent: 23. mars 2004 09:28
>>To: pgsql-general@postgresql.org
>>Subject: Re: [GENERAL] PHP or JSP? That is the question.
>>
>>
>>In terms of getting a page up and working, then PHP likely to be
>>quicker, as its pretty easy to learn.
>>Java kind of demands you learn more "machinary" before doing
>>much, but
>>it may provide you with more capability once you get
>>comfortable with it.
>>
>>In terms of installing and configuring, well PHP is just an Apache
>>module, so it is reasonably easy to get going.
>>To get JSP's going you really need to use a servlet engine
>>(e.g Jakarta
>>Tomcat) - you dont *actually* need Apache httpd at all in this case
>>(there are reasons to have it tho, and there is an Apache
>>module to link
>>'em - mod_jk or mod_jk2).
>>
>>To further confuse, there are a number open source J2EE engines that
>>offer more functionality than Tomcat - (Jboss and Jetty come
>>immediately
>>to mind).
>>
>>Any of these would actually be a good choice - hope I have helped :-)
>>
>>regards
>>
>>Mark
>>
>>Andrew Falanga wrote:
>>
>>
>>
>>>So, what I'm wondering is, which platform offers better
>>>
>>>
>>(more stable,
>>
>>
>>>ease of use, ease of maintainability, etc.) support for developing
>>>such an application. One consideration that has been brought to my
>>>attention is that PHP is natively supported by Apache and
>>>
>>>
>>JSP requires
>>
>>
>>>a separate interpreter (Jakarta or whatever).
>>>
>>>
>>>
>>---------------------------(end of
>>broadcast)---------------------------
>>TIP 8: explain analyze is your friend
>>
>>
>>
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
>.
>
>
>
--
Guy Fraser
Network Administrator
The Internet Centre
780-450-6787 , 1-888-450-6787
There is a fine line between genius and lunacy, fear not, walk the
line with pride. Not all things will end up as you wanted, but you
will certainly discover things the meek and timid will miss out on.
