soap messages over a single HTTP(S) connection

Can anyone give me an answer for the following question: I have a remote web service and a requirement about 100 TPS. (transaction per second ). As far as I know creation of the connection ( HTTP connection ) is quite expensive operation. So, I need to create just one HTTP connection with the web service and bei开发者_JS百科ng able to send a lot of SOAP messages (envelopes) through that connection, so it be not one SOAP message and one HTTP connection, but many SOAP messages and one HTTP connection. Of course I need to create as much HTTP connections as I need, but each of them must serve to some SOAP messages.

May be there is some development pattern or other issue which I do not know.

I would very appreciate any kind of help!

SOAP does not have to be over HTTP. It just happens that it is nearly always implemented over HTTP.

If you really want to use SOAP you can use a socket, or message queue as well as HTTP. For an example see: http://msdn.microsoft.com/en-us/library/51f6ye7k.aspx

However, I think if you need 100 TPS, SOAP is probably not the right technology to use.