SOAP Server
-
We are currently investigating the use of SOAP as 'intermediate layer' between some complex modules. .NET makes it very easy to create a 'Soap DLL' that is activated by IIS. Great. However, we are considering to use this technology to access bigger server-style applications. These applications typically take several minutes to start up, handle a large amount of memory, and therefore cannot simply be recompiled into a kind of 'Soap DLL'. Browsing through the Microsoft documentation I found an excellent AtlServer example that seems to do what I need. However, it would be much nicer if we could use the more modern .NET technology for this. So here are the 'million-dollar'-questions: - Is it possible, using .NET technology, to make a standalone .exe server-application behave like a SOAP-server via the HTTP protocol? - Is it possible, using .NET technology, to make it accept SOAP requests via a message queue as well? - If NO on the questions above, is using the AtlServer a step in the good direction or is ATL a dead-end? - If YES on the questions above, where can I find good .NET examples on writing such a SOAP server? Because I'm not sure in which forum to post it, I'll post it in 2 or 3 forums. Sorry if you get this multiple times. Enjoy life, this is not a rehearsal !!!
-
We are currently investigating the use of SOAP as 'intermediate layer' between some complex modules. .NET makes it very easy to create a 'Soap DLL' that is activated by IIS. Great. However, we are considering to use this technology to access bigger server-style applications. These applications typically take several minutes to start up, handle a large amount of memory, and therefore cannot simply be recompiled into a kind of 'Soap DLL'. Browsing through the Microsoft documentation I found an excellent AtlServer example that seems to do what I need. However, it would be much nicer if we could use the more modern .NET technology for this. So here are the 'million-dollar'-questions: - Is it possible, using .NET technology, to make a standalone .exe server-application behave like a SOAP-server via the HTTP protocol? - Is it possible, using .NET technology, to make it accept SOAP requests via a message queue as well? - If NO on the questions above, is using the AtlServer a step in the good direction or is ATL a dead-end? - If YES on the questions above, where can I find good .NET examples on writing such a SOAP server? Because I'm not sure in which forum to post it, I'll post it in 2 or 3 forums. Sorry if you get this multiple times. Enjoy life, this is not a rehearsal !!!
Patje wrote: Is it possible, using .NET technology, to make a standalone .exe server-application behave like a SOAP-server via the HTTP protocol? Patje wrote: Is it possible, using .NET technology, to make it accept SOAP requests via a message queue as well? Yes and Yes. Use .NET Remoting. Patje wrote: If YES on the questions above, where can I find good .NET examples on writing such a SOAP server? Check out COM+ Web Services: The Check-Box Route to XML Web Services You'll also enjoy Soap MQ Transport, the SOAPTransport Sample. Good luck!
Ian Mariano - Bliki | Blog
"We are all wave equations in the information matrix of the universe" - me -
Patje wrote: Is it possible, using .NET technology, to make a standalone .exe server-application behave like a SOAP-server via the HTTP protocol? Patje wrote: Is it possible, using .NET technology, to make it accept SOAP requests via a message queue as well? Yes and Yes. Use .NET Remoting. Patje wrote: If YES on the questions above, where can I find good .NET examples on writing such a SOAP server? Check out COM+ Web Services: The Check-Box Route to XML Web Services You'll also enjoy Soap MQ Transport, the SOAPTransport Sample. Good luck!
Ian Mariano - Bliki | Blog
"We are all wave equations in the information matrix of the universe" - meThanks, So far I succeeded in writing: - a C# stand-alone SOAP server - a C++ stand-alone SOAP server Next steps are to write: - a .NET C++ class (or example class) that can be embedded in our applications to make it a simple SOAP server. - a .NET C++ class to do the same for SOAP message queue requests. Why C++? Well, the applications are all written in C++ and for the time being we like to keep our applications as 'compact' as possible. I mean, not a bunch of DLL's or components lying around, but a rock-solid executable file that simply needs to be copied on the system. From what I understand from C#, the C# compiler cannot simply create an object file that can be linked with the rest of the application. With C++.NET this is still possible. Enjoy life, this is not a rehearsal !!!
-
We are currently investigating the use of SOAP as 'intermediate layer' between some complex modules. .NET makes it very easy to create a 'Soap DLL' that is activated by IIS. Great. However, we are considering to use this technology to access bigger server-style applications. These applications typically take several minutes to start up, handle a large amount of memory, and therefore cannot simply be recompiled into a kind of 'Soap DLL'. Browsing through the Microsoft documentation I found an excellent AtlServer example that seems to do what I need. However, it would be much nicer if we could use the more modern .NET technology for this. So here are the 'million-dollar'-questions: - Is it possible, using .NET technology, to make a standalone .exe server-application behave like a SOAP-server via the HTTP protocol? - Is it possible, using .NET technology, to make it accept SOAP requests via a message queue as well? - If NO on the questions above, is using the AtlServer a step in the good direction or is ATL a dead-end? - If YES on the questions above, where can I find good .NET examples on writing such a SOAP server? Because I'm not sure in which forum to post it, I'll post it in 2 or 3 forums. Sorry if you get this multiple times. Enjoy life, this is not a rehearsal !!!
Have a look at gSOAP[^]. Its a clean, fast way to put a SOAP interface onto C/C++ programs. The server code generated is small and fast enough to be used in embedded systems, and has no nasty dependancies. So, for gSOAP.
- Is it possible, using .NET technology, to make a standalone .exe server-application behave like a SOAP-server via the HTTP protocol?
Yup, HTTPS too.* Is it possible, using .NET technology, to make it accept SOAP requests via a message queue as well?
Not directly using gSOAP, but you can create asymetric methods. You would need to create a proxy to get them to/from the SOAP service.
Ryan.
- Is it possible, using .NET technology, to make a standalone .exe server-application behave like a SOAP-server via the HTTP protocol?
-
Have a look at gSOAP[^]. Its a clean, fast way to put a SOAP interface onto C/C++ programs. The server code generated is small and fast enough to be used in embedded systems, and has no nasty dependancies. So, for gSOAP.
- Is it possible, using .NET technology, to make a standalone .exe server-application behave like a SOAP-server via the HTTP protocol?
Yup, HTTPS too.* Is it possible, using .NET technology, to make it accept SOAP requests via a message queue as well?
Not directly using gSOAP, but you can create asymetric methods. You would need to create a proxy to get them to/from the SOAP service.
Ryan.
Thanks Ryan, I looked at gSoap but because of its GPL license we cannot use it in commercial software. Although a commercial license for gSoap exists, I further looked into the .NET classes and since they are free (but tied to the Windows platform which isn't a problem for us) .NET looks the way to go. So far I made a successful small .NET .exe SOAP server, and I'm looking further into embedding SOAP logic in our server applications that way. Thanks anyway for your information. Enjoy life, this is not a rehearsal !!!
- Is it possible, using .NET technology, to make a standalone .exe server-application behave like a SOAP-server via the HTTP protocol?