What’s the RPC secret?

Tim observes
I think one of the reasons that the RPC model still dominates many people’s thinking is that we really haven’t gone beyond the HTTP binding defined in the first SOAP spec.

Agreed. Recently I observed two phenomena that might well be the main reasons the RPC model dominates: First, many of the people working on Web services standards bodies come from an OMG standards background. Second, many companies building Web service platforms (including some major vendors) view SOAP as just another wire protocol under their platform’s existing programming model. Very few platform vendors have internalized service-oriented architectures and the Web services potential.

Comments (2)

  1. Anonymous says:

    About the common misinterpretation of ‘all things Web Services’ : Christian Weyer: Web Services & .N

  2. Chris Kinsman says:

    I have been looking at both but I have yet to see a compelling treatise that indicates why/how a non-RPC model makes sense. Folks talk about it but I have yet to see .NET code that doesn’t just give lip service to messaging but instead does something with it that can’t be done in the RPC model.