The limitations noted below are incorrect. PHP can use Java classes, is strongly OOP, and is best implemented using the same architectural design as you would with JSP/Servlets/JavaBeans. However, like ASP, PHP can be implemented easily using NON-OOP techniques, so a programmer can pick up bad programming habits.
On a positive note, a programmer already versed in ASP development will find PHP easy to learn and, because of the language syntax being roughly similar to Java, so will Java programmers. Also, JSP hosting is truly more difficult to find; PHP seems to be everywhere. One thing I have found is that is very easy to implement PHP on a hosted site page by page, section by section, or just about in any way you would want, so you can implement very quickly and change the content of any file at any time. For small interactive sites that are constantly growing, PHP would provide a reasonably development method. Perhaps the main factor is the necessary speed. If you have a large site where speed is of prime concern, JSP and Servlets provide a faster solution (all other things being equal). Where speed is not so important and changes are being made daily to the code, I would recommend PHP. I have interacted with many sites that use PHP today successfully, and I feel that it remains a viable development solution. HOWEVER, development in PHP is best done using the same separation of presentation and logic that JSP provides. -----Original Message----- From: Daniel Jaffa [mailto:[EMAIL PROTECTED]] Sent: Monday, May 13, 2002 6:53 PM To: [EMAIL PROTECTED] Subject: Re: comparing JSP/PHP You are also not looking hard enough for shared java support. You can get it for free at several sites. And you can find many hosting companies offering support. Daniel Jaffa Java Developer -----Original Message----- From: A mailing list about Java Server Pages specification and reference [mailto:[EMAIL PROTECTED]] On Behalf Of G.Nagarajan Sent: Monday, May 13, 2002 4:16 AM To: [EMAIL PROTECTED] Subject: Re: comparing JSP/PHP hi, Here are some advantages of using jsp over PHP. I have not worked with PHP but it is like asp, so some features listed below might be available. 1. JSP pages are compiled into a java class (servlet) during the first invocation. The subsequent requests are then served by the compiled class. In the case of PHP, the code is interpreted and executed for each request. 2. JSP uses java code while PHP uses its own syntax. 3. We can easily use OOPs techniques in jsp. Complex code can be put into java classes and they can be invoked from the jsp page. We can invoke the java interpreter from PHP but that would not be an elegant solution. 4. JSP provides tag libraries which can be used to hide the java code even further. Basically, in my opinion, if the client's applications needs only some simple scripting then PHP will be a good option. If there are lots of complex logic, with database access etc then jsp with servlets would be a better option. Writing lots of loops, ifs and exceptions in a page mixed with html and javascript will a nightmare. Then you also will have to worry about the html design etc. regards, Nagarajan. > -----Original Message----- > From: A mailing list about Java Server Pages specification and reference > [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Lynn > Sent: Monday, May 13, 2002 6:28 AM > To: [EMAIL PROTECTED] > Subject: comparing JSP/PHP > > > OK, so I got a bit of an odd question here. I've been programming internet > applications for a few years now and I started with JSP because > of a previous > background with Java applications. However, I've found that in my > area, getting > shared hosting with Java support is the next closest thing to > impossible and is > usually very expensive. For this reason I've had to switch to > mostly using PHP. > > I would be very interested in knowing what the comparitive > strengths and weaknesses > are between the two languages if anyone out the is knowledgable > in both. Though > monetary limitations usually force me into PHP, I would like to > be able to make an > educated decision on wether it's worth pushing a client towards JSP. > > Thanks much, > > Daniel Lynn > Mystic Productions > > ================================================================== > ========= > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff > JSP-INTEREST". > For digest: mailto [EMAIL PROTECTED] with body: "set > JSP-INTEREST DIGEST". > Some relevant FAQs on JSP/Servlets can be found at: > > http://archives.java.sun.com/jsp-interest.html > http://java.sun.com/products/jsp/faq.html > http://www.esperanto.org.nz/jsp/jspfaq.jsp > http://www.jguru.com/faq/index.jsp > http://www.jspinsider.com ======================================================================== === To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
