Why is soap.inproc not supported for production use?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

lbagnall - 29 Sep 2004 11:53 GMT

I am designing a web service using WSE 2.0 that has flexible deployment
requirements. In particular, sometimes the client and service will be on the
same machine, and sometimes it will be going over the Internet. In the
latter case, I'm obviously going to use the HTTP transport. For the former,
I'd like to just use soap.inproc. However, I found the following comment in
the WSE 2.0 Service Pack 1 Readme.

"The soap.inproc transport protocol is not supported for production
environments. That is, the soap.inproc protocol, which can be used to send
SOAP messages to and from components within the same application domain using
the WSE Messaging API, is for testing purposes only."

Why? I guess I can use the TCP protocol over the local loopback, but it
seems unnecessarily inefficient, when soap.inproc would let you do the
communication in memory.

Reply to this Message

Tomas Restrepo \(MVP\) - 30 Sep 2004 03:34 GMT

> I am designing a web service using WSE 2.0 that has flexible deployment
> requirements. In particular, sometimes the client and service will be on the
[quoted text clipped - 11 lines]
> seems unnecessarily inefficient, when soap.inproc would let you do the
> communication in memory.

You're missing a critical part of the doc: "within the same application
domain". Thus, soap.-inproc only works when the receiver and sender reside
inside the *same* process (not same machine) and within the same .NET
application domain.

As for why it is not fully supported, I'm not sure, but I'd guess that
because of its limited functionality, and the fact that there are probably
not many scenarios where it is truly useful, they didn't allocate all the
resources necessary to stress it and test it as well as the other
transports... but that's just a guess!

Signature

Tomas Restrepo
tomasr@mvps.org

Reply to this Message

Benjamin Mitchell - 30 Sep 2004 15:51 GMT

Exactly as Tomas says, if you want to use WSE to send messages between
applications on the same machine and want to avoid HTTP you need to use
soap.tcp, rather than soap.inproc.

Regarding why soap.inproc is not supported for production use I know that
Keith Ballinger described soap.inproc as mostly useful for testing purposes
in his talk at TechEd.

"Tomas Restrepo (MVP)" wrote:

> > I am designing a web service using WSE 2.0 that has flexible deployment
> > requirements. In particular, sometimes the client and service will be on
[quoted text clipped - 26 lines]
> resources necessary to stress it and test it as well as the other
> transports... but that's just a guess!

Reply to this Message

Rate this thread:

Why is soap.inproc not supported for production use?

Free Magazines