Home/ Questions/Q 1102461
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T01:11:24+00:00

The brand-new WCF-based code needs (in the meanwhile) to provide a service to a

  • 0

The brand-new WCF-based code needs (in the meanwhile) to provide a service to a legacy code that works in plain HTTP. So that, along with new SOAPed requests, I need to tailor some oldskul-style communication (on a different port): to be able to receive plain HTTP, analyse the request body and send the plain HTTP with some body in response.

Looked at the System.ServiceModel.ServiceHost API but couldn’t find anything appropriate. Any advice will be generously accepted. It is strongly preferred to leave the legacy code as it is, do I have a real choice here? Thanks in advance!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think the main question is how your service and the body of your messages are defined.

    WCF currently has more flexibility allowing for sending and receiving non-SOAP XML messages, JSON, ATOM, ATOMPub, … but if you are sending plain text or custom format as the body of your messages, WCF is probably not the way to go.

    So what is your message body?

    UPDATE

    WebHttpBinding is the way to go: http://msdn.microsoft.com/en-us/library/system.servicemodel.webhttpbinding.aspx

    • 0