I totally love it that Tim Ewald now has the time to post more to his blog. I enjoy reading what he writes quite a lot. In particular, I love it how he approaches things I've been pondering on for a while and helps me clearly understand that I really don't fully understand it at all ;)

Ohh, and btw, I soo agree with his comment on how toolkits could implement stateful services:

"My concern about using EPRs to reference stateful instances of services actually depends on how toolkits choose to implement it. If a toolkit dispatches a call to an object instance that lives just long enough to process the input message and generate an output message (if any) and leaves it to that object to map additional header info to some sort of state management mechanism, that might be okay. If a toolkit does that mapping for you, i.e., it uses the header info to map to an object that maintains state, that would not be okay. The difference is that in the first case, the developer is forced to be deliberate about how state is managed in their system"

This is a really good example about how you want a toolkit (or framework, or whatever) to handle the mundane tasks, but leave the important ones to the developer.


Tomas Restrepo

Software developer located in Colombia. Sr. PFE at Microsoft.