Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m developing a WCF-based API for my company’s CRM software. In the future, it will be used to develop applications on multiple platforms. I know WCF provides named pipe, TCP, and HTTP transports, but should I bother with the complexity of supporting all three when everything seems to be using RESTful HTTP these days?
REST is the architectural style of the web, not just xml files over htttp without SOAP.
WCF is a framweork with the sole purpose in life is to abstract developers from the underlying platform / protocol / stack of specs. WCF REST was a poor addition to the toolkit to let you expose POX services.
RESTfulness requires distribution, lack of session, designing of custom media types or reuse of existing ones, and many other properties you need to think about. Designing a REST architecture is as much about xml ove rhttp as designing an SOA one is about having a soap envelope.