I'm building an iphone application that will need to communicate and exchange data with a server.
My plan is to exchange messages in SOAP format and have PHP/Apache handle the processing/response. My question is, what could Tomcat/JSP/Servlets do that Apache/PH开发者_开发百科P can't?
With out any more information than "exchange SOAP messages", the answer would be "nothing".
Fundamentally, you'll likely be able to do whatever you want in some way with either, so pick the one you're most familiar with.
The biggest difference between LAMP and "The Java approach" is the added step of compilation. All of the languages I've heard attached to LAMP (Perl, Python, and PHP) are languages where source code is interpretted, whereas Java interprets bytecode. It sounds like a small difference, but in practice, compilation adds on a non-trivial amount of effort.
I just hope that the Java folks look at LAMP with an open mind , and likewise I hope that the LAMP folks look at Java with an open mind. Java does some things well, and does other things not so well. Likewise, LAMP does some things well, and other things not so well. Maybe we can learn from both.
精彩评论