Monthly Archives: November 2004

The architecture of protocol independence

Well I was hoping somebody would take an actual kick at the can in response to my challenge, but I suppose a promise is better than nothing. 8-) Ok then, I’ll offer my opinion. I don’t think it’s possible (to describe protocol independence as a constraint), because I believe that the choice to be protocol… Read More »

zTroutgirl

Joyce heads to CommerceNet‘s zLab. Well, duh! Who couldn’t see that one coming after what went down this summer? 8-) Congratulations to Joyce and to CommerceNet.

MEST up

Oh come on, somebody had to say it. 8-) Savas and Jim rename their architectural style, formerly known as “ProcessMessage”, MEST. Not much to see yet, but they’re writing a couple of papers, one of which will go into detail about MEST’s architectural constraints, permitting us to evaluate its suitability at large scale, it’s relationship… Read More »

A protocol poser

Here’s a challange for fans of protocol independence; try to describe it in strict architectural terms, i.e. in terms of constraints applied to components, connectors, and data.

Generic vs. specific state setting

David Orchard again tries to defend the Web services stack by analyzing where service-specific state-setting operations are required. His conclusion is unsurprising; This article has shown that specific write operations are the correct interface design choice for many complex update operations. There are also constrained situations where generic update operations such as HTTP PUT provide… Read More »

EPR/URI warnings

David asks; I always appreciate it when Mark mentions me, but I’m not sure what warnings I’m heeding. I meant those I mentioned in a my heads up to the TAG. Which, FWIW, discusses (sort-of) value in an epr URI scheme; a potential answer to your “Others?” question about how the EPR/URI mapping could occur.… Read More »

Numero uno

Issue number one for the WS-Addressing WG; The Architecture of the World Wide Web, First Edition indicates that distinct resources must be assigned to distinct URIs. This must be considered when refining the mechanism for the service specific message headers. Oh, the irony (and not the Alanis kind).