Sunday, May 20th 2018, 12:11pm UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.



Date of registration: Jul 17th 2012

Posts: 47


Monday, February 23rd 2015, 10:37am

gSoap Compatibility

I am working on to port gsoap to Embos. But am not able to succed. Since I wanted client - server architecture by using webservices.
Our goal is that wanted a webservice which is running any of the server like IIS and by gsoap methodology try to invoke the methods running in server.
Do you guys having any support for gsoap. Because gsoap works on different platforms.
If its there how we can proceed with that to host webservice in server.

SEGGER - Oliver

Super Moderator

Date of registration: Nov 14th 2007

Posts: 41


Thursday, February 26th 2015, 9:43am

Hello Venkat,

As embOS/IP does not have native support for SOAP you will need to implement it yourself in one of the following ways, depending on client/server that you want to setup:

For a client a SOAP request is a simple POST message sent via TCP. So basically this is connecting to a Web server that runs a SOAP service, sending a POST request and parsing the XML answer you get back. All this needs to be done by your application.

For a server that already runs the embOS/IP Web server you can register a path with our REST API to forward the whole POST request froma SOAP client to a callback. You can then parse the XML request and send back your XML answer directly from the callback using the IP_WEBS_* API. Parsing the request and assembling the answer to send back needs to be done by your application.
Please be aware that you have to either send a HTTP/1.0 request to the server to completely disable chunked encoding (content might be received in multiple encoded chunks) or you send a HTTP/1.1 request and have to deal with chunked encoding in your client.

Best regards,