I work for Red Hat, where I lead JBoss technical direction and research/development. Prior to this I was SOA Technical Development Manager and Director of Standards. I was Chief Architect and co-founder at Arjuna Technologies, an HP spin-off (where I was a Distinguished Engineer). I've been working in the area of reliable distributed systems since the mid-80's. My PhD was on fault-tolerant distributed systems, replication and transactions. I'm also a Professor at Newcastle University and Lyon.
Tuesday, February 27, 2007
Nooooooooooo!!!!!
This just got pointed out to me through the minutes of the first day at the W3C workshop onWeb of Services. I must have missed this stirling move on the part of the TAG. I've mentioned before about sessions and Web Services and how WS-Addressing is not the right way of doing this, but WS-Context is better. Of course it's no surprise to see that contributions to this TAG effort are from heavy WS-Addressing users, but us WS-Context supporters need to be more pro-active.
This is not to say that WS-Addressing and WS-Context can't be used together: they can and they are. What I'm pushing for us "using the right tool for the right job". Let's use WS-A for addressing and routing of messages, and WS-Context for session and state management.
ReplyDelete