Roberto
Roberto

Reputation: 1944

SOAP replacements/workarounds/libraries in PHP

Being as stubborn as it gets, I'm building my own PHP-based CMS and framework (named RAmen/FSM just for the kicks) that has been deployed multiple times for my customers. Now, I'm going to develop a support ticket application for it that I will deploy on a 'central' server for convenience of maintenance.

Now, I've looked into SOAP services and was happy until I got to WSDL generation in PHP and in itself. So, what would you suggest for me to 'securely' (as in, no https) manage this with SOAP-like simplicity on the client side ($support->newTicket), without the WSDL headaches on the server side? Or should I –gasp– stop being so stubborn and just go with a PHP library (in which case, please do recommend!)

Thank you, fellow pastafarians/spagnostic coders!

Upvotes: 0

Views: 351

Answers (2)

troelskn
troelskn

Reputation: 117487

PHP has a native SOAP extension, that automates client as well as server. It is a little buggy in some places, but still better than nusoap (IMHO).

That said, I would never chose SOAP if I had any bearing on the decision. Use xml-rpc or a rest-based approach.

Upvotes: 2

Bluephlame
Bluephlame

Reputation: 3969

I have a similar question, whether to use REST or SOAP. I am using REST but that is beacuse i want a simple API like function not so much the rigid functionality associated with REST.

That being said here is a nice little library to get you started on SOAP

http://sourceforge.net/projects/nusoap/

By the sounds of it SOAP is actually what you want. you will fin it a bit easier to implement as you get the domain models from the WSDL.

Upvotes: 1

Related Questions