Reputation: 1560
Can you give examples how you used gSOAP and how well it was integrated in your existing architecture? Have you found development bottlenecks with gSOAP?
Upvotes: 3
Views: 1159
Reputation: 11
We used gSOAP in a web server on ARM ARM9 400MHz device. gSOAP daemon connected to a database daemon through zeromq library, which is run on the same device.
It supports more than 1000 basic requests wich does not requre connection to database.
Disabling support for multi-referenced SOAP option by the WITH_NOIDREF define helped to decrease serialization time about 4 times faster on big requests with large number of serialization nodes.
Upvotes: 0
Reputation: 86
We used gSOAP for a bunch of ARM clients to communicate with an AXIS Web Service server. Pros of gSOAP:
However, we ran into several development bottlenecks:
Upvotes: 4
Reputation: 15571
We are using gSOAP to consume a WCF based webservice from an application deployed on a linux device running on ARM processor. The experience is good to a large extent.
Upvotes: 1
Reputation: 18347
We are using gSoap to deploy a web service onto an embedde linux device running an ARM MX processor.
Upvotes: 1
Reputation: 21022
We used gSOAP in a C++-based web server about 4 years back. Overall it worked fine. The only major issue was that the interface was in C and procedural (I understand it is difficult to design a good non-procedural interface). There may be a lot of repeated code while implementing the interface, for which you might have to use macros (we didn't explore the templates option too far then).
Upvotes: 2