1.
I'm supposing here, but I think the HTTP connection really means "OCX/ActiveX/whateverXitistoday used as a web service in IIS and .NET".Get them to spell this out in a design meeting.
2. Suggest that this decision be left for later, when several competing strategies can be tested. Abstract the communication process.
3. When it comes time to finalize the comms, remind them:
The code needs to be very, very fast, and the trade-off is memory for speed...One of those few applications that really *does* need to be extremely efficient.
4. Show the native socket app blowing .NET out of the water.
5. Reintegrate the abstracted comms code for a final speed improvement.
Ooh, I can work this Team Thinking, can't I? >:)