Hi Patrick!
On Mon, 12 Jun 2000, Patrick Kay wrote:
> Hi folks. A little help please...
I am not a very experienced developer in JSP but I can contribute
with my opinion on both:
(note that you will surely find even more authoritative answers with
a bit of search on java.sun.com)
> I'm tying to convince my manager that we should be developing in JSP and not
> go to PHP.
Also note that PHP ,starting with version 4, includes support for 'talking'
to Java and Servlets APIs, thanks to Sam Ruby from the IBM team.
> Here are my arguments. Comments and additions please?
>
> -JSP allows for the use of all the Java features including JDBC, integration
> with servlets, and full use of object oriented design and programming.
...and the comming connectors will bring an even more 'normalized' access to
EISes. PHP's database API is very heterogenic. the 'Pear'(PHP extension and
add-on repository) aims to correct this, among others, but it's in a very early
stage.
> -JSP�s pure java support means that anyone who knows Java can code for JSP.
That is a very strong one. A company that has a team of Java programmers can
easily 'guide' them toward Internet applications, and the change it's not so harsh.
But PHP is also pretty easy to learn (compared to Perl, for example.)
> There is no propriety language to learn. Java is well supported and
> documented. Training and books are easy to find. Employees are willing and
> eager to learn and use Java. It will be more difficult to find developers
> with PHP skills than JSP skills.
Now, to be honest, PHP it's not proprietary either. OTOH, the documentation it's
still under refinement, after the load of work which brought lots of new features
to PHP4 (sometimes you do have to RTFS.)
> -JSP will allow for easy integration into an eventual Enterprise Java Beans
> architecture should company_name decide to scale operations with an
> application server. This is a major consideration.
Yap, it fits well into a J2EE centric enterprise. The J2EE platforms offers
extremely important facilities for the middle-tier programming, like state
management, session and transactions (including distributed transactions.)
The EJB architecture is far more robust for large applications, and PHP lacks
good support for a complete OO approach. The OOP support is rather in an
early stage, IMHO.
> -JSP is widely supported across major web servers due to the popularity of
> Java. PHP, however is currently supported on Apache only:
false. PHP is supported on a lots of others, including IIS and Netscape,
Zeus and AOLServer (and Roxen , iirc). On this side, I think it has a far
better mark, given the fact it's also Open Source [ and now good Servlets/JSP
servers costs some $$ -- still there is Tomcat and former Jserv, and several
others ]
> �The second, and most popular, method is to run PHP as a module in a
> multiprocess web server, which currently only includes Apache.�
see above.
> -JSP has wide industry support, with major industry players contributing to
> its specification. (See java.sun.com/products/jsp/industry.html)
that is another major point taken.
Still, PHP fits well in much of the small 2 medium web development needs,
but JSP/Servlet/EJB [aka J2EE arch.] seems to fit even better for large
projects [I am biased for J2EE and I talk from papers, no experience :)]
As you seem to have missed lots of details of PHP, please visit www.php.net/
www.zend.com to find out more.
And concerning speed, Resin I think claimed to be faster than PHP, but I dunno
if they tested against a fined tuned PHP4, or even PHP4 not PHP3.
regards,
-- teodor
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
