SEDA

At the recent XML Summer School I mentioned SEDA - Staged Event Driven Architecture - as an interesting approach to temporal decoupling a form of decoupling which I believe is vital to any non-null definition of SOA.

I think of it now because it is relevant to Restaurants, roller coasters and randomly failing web applications.

Who you are

A while back I asked "Who are you?.

I recieved somewhere in the region on 40-50 replies via various media. Here is a distillation.

• You are interested in Python/XML/Web Services/SOA and a goodly number of you are interested in broader areas of dynamic typing/information integration/distributed systems.
  
• Many of you like the ITWorld articles citing humour, interesting/odd-point-of-view and writing style as reasons.
  
• You mostly work in IT in the commercial sector
  
• You live in North America/Europe
  

Thanks to all who replied.

Fast pipe. Always on. Get out of the way.

"I used to think that it was only a matter of time before the web was 'fixed' to provide reliable message exchange functionality without which, B2B message exchange on the Web would be impossible. I do not think that any more." -- Fast pipe. Always on. Get out of the way.

Restaurants, roller coasters and randomly failing web applications

"this is a temporally decoupled web application folks, POST your required transaction, take an idempotent URI and poll for latest service information."--
Restaurants, roller coasters and randomly failing web applications