If SOAP is now considered overengineered over REST why isn't WCF? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 9 years ago.

I'm amazed that years over years IT pretend to simplify communication or software design and a few years later it declare it was over-engineered. EJB, SOAP, so looking at all the WCF stuffs do we as users (not as Microsoft or IBM who need to sell new stuffs) really need it ?

Update: this is a concrete example http://www.go4answers.com/Example/expert-interoperability-issues-ws-736.aspx The guy knows how to call a server with WS-Security using old soap and in WCF it seems it doesn't really help and worst it seems even more complicated as it is said:

"WCF has still some limitation - not all WS-Security configuration are possible without custom development."

Nobody seems to be able to have found a solution.

So can people instead of mere opinions give concrete examples (with source code both in wcf and in soap or rest for comparison) of hard problems (and not easy problems) that can be solved by WCF more easily than can be with traditional soap ?

c# java web-services

задан user310291 8 October 2010 в 17:54

0 ответов

Другие вопросы по тегам:

c# java web-services

If SOAP is now considered overengineered over REST why isn't WCF? [closed]

0 ответов

Похожие вопросы: