My blog has moved and can now be found at

No action is needed on your part if you are already subscribed to this blog via e-mail or its syndication feed.

Sunday, February 25, 2007
« Reactivity and Cisco - Another consolida... | Main | Winter is still with us... »

I recently had the opportunity to look at some of the details of WSRP v1 WSDL InterfacesWeb Services for Remote Portlets (WSRP), which is a web services protocol for aggregating content and interactive web applications from remote sources.  As an aside, if you are interested in a quick tutorial, I would recommend the OASIS WSRP TC's Web Services for Remote Portlets 1.0 Primer.

The interesting thing with this standard is that it is built on top of a few fundamental standards such as XML, SOAP and WSDL. But with WSRP, every single web service has the same set of operations (See graphic).

This is very similar to the REST architectural constraint of uniform interfaces, which means that all resources present the same interface to clients. As noted in Steve's excellent REST Article:

"A significant advantage of the uniform interface constraint lies in the area of scalability. For a client to correctly interact with a SOA service, it must understand the specifics of both that service’s interface contract and data contract. But for a client to invoke a REST service, it must understand only that service’s specific data contract: the interface contract is uniform for all services."

To apply this to WSRP, both the interface contract and the data contract are uniform for all WSRP services, and as such the consumer of the WSRP service is a generic construct. For example, pretty much all of the major portal implementations supply, at a minimum, a WSRP consumer portlet that can bring in a remote WSRP service without any coding.

While I understand that REST is about more than uniform interfaces, wonder what the REST folks would have to say about WSRP.

2/25/2007 1:28 PM Eastern Standard Time  |  Comments [2]  |  Disclaimer  |  Permalink   
Sunday, February 25, 2007 4:40:35 PM (Eastern Standard Time, UTC-05:00)
I'm not sure whether I count as one of the "REST folks", but similarly to WS-Transfer, the question seems to be "why bother"? First, invent a new protocol stack and tunnels everything through HTTP POST, then use it to implement something on top that is already there below? Seriously - what "transport" other than HTTP is anyone ever going to use for WSRP? Why not use HTTP directly?
Tuesday, February 27, 2007 2:09:41 PM (Eastern Standard Time, UTC-05:00)
All components support the same interface, but that interface isn't uniform nor even very general at all. I don't see this as much different than all stock quote services implementing getStockQuote.
Comments are closed.