|
|
(4 intermediate revisions by the same user not shown) |
Line 1: |
Line 1: |
| Two main approaches:
| | *[[websockets]] |
| * [http://en.wikipedia.org/wiki/SOAP SOAP]: HEAVY, uses a formal interface with info packaged as XML for delivery across HTTP; interface formats includes WSDL, XSD | | *[[RESTful web service development]] |
| * [http://www.xfront.com/REST-Web-Services.html REST]: LIGHT, uses HTTP to define interface, including HTTP verbs (GET,POST,PUT,DELETE) + URL parsing + URL parameters
| | *[[SOAP]] |
| | |
| Available technologies:
| |
| * SOAP: Java 6 (baked in, nice), [http://au2.php.net/manual/en/book.soap.php PHP], Apache Axis2 (Java or C), gSoap, Spring's "contract first", .net (haha)
| |
| * REST: Apache Axis2 (Java or C), PHP HOWTO's [http://www.gen-x-design.com/archives/making-restful-requests-in-php/ 1] [http://www.fliquidstudios.com/2009/01/13/introduction-to-writing-a-rest-server-in-php/ 2], [http://www.recessframework.org/section/tutorials PHP recess library] | |
| | |
| ---
| |
| | |
| No doubt in my mind, we're going with [[RESTful web service development]]...
| |