Web services are intended to allow existing applications to communicate
with each other. So, for example, if you have a large web-based
e-commerce store written in PHP, and you want to allow arbitrary
inventory or accounting applications to integrate with the store,
the most natural scheme is to expose some of the store's methods
as web services. That means web services in PHP.
To instead construct a Java or .NET application alongside the store
and have them communicate with the store is some way, would be to
add additional complexity and an additional fault point, for no gain.
Jonathan Schilling
------ Original Message ------
From: Erik <eriklaubsch@web.de>
Date: Friday, December 23rd, 2005 11:16 PM MST
To: soap@lists.php.net
Subject: Reasons to use PHP for Web Services
Since I am trying to convince a teacher of mine to include Web Services /
SOAP and PHP as a compulsory optional subject for the next term I've spent
quite some thinking about reasons to use PHP when implementing web services.
His main argument against PHP is that every enterprise uses .net and java
for web services anyway and that there does not seem to be a reason to use
PHP at all.
So my questions are:
Why use PHP for Web Services?
Are there any cases where PHP is the superior choice?
Are there any cases where PHP is the only choice?
(I've got a few good answers on those questions myself but would like to
make sure that I'm well prepared and convincing the next time.)
Thanks in advance
Erik
--
PHP Soap Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Soap Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
