WebService approach - HTTP limitation

Question

Hello,
This is a PI architectural question, rather than a PI development one.
One of the scenarios to be used contemplate an WebService approach but I've been told that there are some technical limitations in using this approach.
Two of them are well known and won't constitute a surprise but the third one came out of the blue. Here are the limitations:
1. payload dimension of xml messages (transport layer);  (Known)
2. serialization of xml on the sender and receiver endpoints      (Known)
bold3. HTTP protocol limits to 2 simultaneous connections between each pair of systems bold
I've found that HTTP 1.1.(RFC 2616 - Hypertext Transfer Protocol -- HTTP/1.1) states that, "A single-user client SHOULD NOT maintain more than 2 connections with any server or proxy", is that what they mean?
How do you understand this limitation? Have you come across this problem?
Thanks in advance,
Gonçalo Mouro Vaz

Answer 1

The below document gives idea about principal propagation in 7.1 and 7.0. I dont know what we have in 7.3.
I think it is possible non sap or sap inbound to sap outbound scenarios using Prinicipal Propagation.  At PI inbound side any authentication mechanism is possible whereas on the PI outbound side only SAP Logon TIcket supported. This is the case for PI 7.1
Please refer this for understanding:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/808d3048-638c-2a10-35a6-faa48e50ad59?QuickLink=index&overridelayout=true