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 !!!
I'm no expert, but this scenario may be a good candidate for .NET Remoting. For more information, check out http://ingorammer.com/remotingfaq/ Marcie CP Blog[^]
-
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 !!!
I'll second Marcie's suggestion to use .NET Remoting in the place of a web service. IIRC, remoting objects can use HTTP as a transport and process SOAP messages out-of-the-box. If it is not built in functionality, then I'm positive that you can add support for both. Google will probably yield some results in that area. The question that pops out at me is why you're looking to do this using HTTP/SOAP. Unless you'd like to have your objects publically availible as a webservice, I'm not so sure that HTTP/SOAP would be the best implementation, IMHO. Using a TCP transport and binary messages would certainly offer lower overhead and better performance. The link Marcie listed for Ingo Rammer's site can offer much more knowledgable and in-depth advice that I ever could. You may also want to look at this[^] article on MSDN on using SSPI security with .NET remoting, if security is a concern. Hope that helps a bit. :) --Jesse
-
I'll second Marcie's suggestion to use .NET Remoting in the place of a web service. IIRC, remoting objects can use HTTP as a transport and process SOAP messages out-of-the-box. If it is not built in functionality, then I'm positive that you can add support for both. Google will probably yield some results in that area. The question that pops out at me is why you're looking to do this using HTTP/SOAP. Unless you'd like to have your objects publically availible as a webservice, I'm not so sure that HTTP/SOAP would be the best implementation, IMHO. Using a TCP transport and binary messages would certainly offer lower overhead and better performance. The link Marcie listed for Ingo Rammer's site can offer much more knowledgable and in-depth advice that I ever could. You may also want to look at this[^] article on MSDN on using SSPI security with .NET remoting, if security is a concern. Hope that helps a bit. :) --Jesse