c++ - Network programming: SOAP vs DIY marshalling with XML library? -

I know there are already a lot of discussions about alternative mechanisms such as SOAP, bloat, XML, and REST. / P>

The situation here is based on the difficulty of applying the protocol by hand, a new team member is actually talking on SOAP. He recommends GSOAP (the project is in C ++.) He tells things like WSDL, cleansing many disturbances by hand coded C ++.

I am currently doing the largest networking with XML based text messages, and XPRAT XML Library. That's why I'm associated with some programming effort (not much) adding to the modifications or message lists of message formats. At the end of the sender, I compile an XML request and send it to an old TCP socket. On the receiver, I parsed the XML using XML or SAX. e.t.c. Has worked fine till now. XML messages are quite compact and most are two hundred pairs. And I understand everything in those messages.

We should use a web site (a server) that is coded using PHP. It is partly running this idea here that a SOAP interface for script writers would be "easy". Everyone on this project believes that SOAP is their salvation.

I see the beginning of GSOP as a major disaster for a large library such as a matured project.

What am I thinking if SOAP is a different and more compact way of doing what, and to make the claims of GSOP or other SOAP equipment easier to make life of development more difficult than reality.

IE, I'm being told that WSDL is better, easier, and more workable, etc. Hand coding from C ++, using an XML library. That it holds the words of C ++ objects right in the announcement of network messages. The thing is, I did not map a different object to any one at the end of getting one of the XML messages I defined.

Or, it is possible that I am worried about nothing

But as a reality, I scan the messages here, I have been told locally whether There is a paradox. I think that you think PHP developers are more likely to like resigned interfaces. There is a 2003 article about this.

Cool interfaces are a growing event and if you need to attract developers to your platform then you will be easy to catch the wave.

After saying this, can not you support multiple interfaces? It is quite common in web services, who do not have captive audiences, you can support your legacy model, a clean race model and a SOAP / WSDL model. Then after 6 months, take the shares after one year, to see which model is the most popular and at least an effort to support.

When it comes to making the site more accessible to outsiders, the rest is more widespread as far as your project is saving, SOAP may do this because it is designed for interface design In certain quantities, it demands hardness, though it can be said about the rest. If this is an important criterion, then you should probably leave the hand-coded XML and go with a high-level interface design that can be applied as both the rest and the SOAP.

I know some people believe that SOAP and the rest are basically different approaches, but if you take a lucrative approach to interface design, then you have to make a bigger SOAP version There should be no difficulty. Although do not try to do this in another way around it.