-
I was reassured that our WS-GAF ideas are correct
I just got out of a loooong session with the authors of the WS-Resource Framework specs. From what I’ve heard, I am now reassured that our WS-GAF ideas were all spot on. In fact, many of the things we have been talking about are part of the current thinking of the authors. I still have…
-
Mark Baker agrees
I should have added to my previous post that Mark agrees with the approach of building distributed applications around the concept of resources (identity+interface+state)… but that’s to be expected given Mark’s view on REST.
-
Mark Baker on the WS-Resource spec
Although Marksees it from a REST point of view, I agree with him about the coupling of identity plus interface plus state. They are re-inventing distributed objects.
-
WS-Resource Framework released
Half of the WS-Resource Framework suite of specifications was made available from Globus and IBM today. Steps towards to the right direction were made (factorisation, lack of overloading of the term “service”, removal of Grid Service Handle/References, removal of Service Instance Factories). However, from an initial first look, it seems that the conceptual model remains…
-
Mars-related photos…
Another one 🙂
-
Starbuck’s on Mars!
I saw this “Mars-Seattle humour picture” on Robert Scole’s blog.
-
Going to San Francisco tomorrow
I am travelling to San Francisco tomorrow. It’s going to be a long long journey. Time to catch with some work then… I bought “Astronomy: The Evolving Universe” for this journey, which I hope to read on the plane. I need an introduction to astronomy and astrophysics for the application we are going to build.…
-
Travelling ahead
I am off to Sheffield for the myGrid integration fest tomorrow and then to San Francisco for GlobusWORLD and the GGF DAIS-WG face-to-face. I will be back in Newcastle on the 29th. These trips should give me the opportunity to do some more work on my blog engine and finish the papers I am working…
-
Another interesting read on “Web Service Sublimation”
“In a tightly-coupled system, the contract between two parties is very specific – message formats are strictly limited as to their content. In a loosely-coupled system, the contract between two parties is more flexibly – message formats are more flexible and extensible. Even with XML, if you want an application to be loosely-coupled, you have…
-
Interesting read on “Web Services = or != distributed objects?”
This post is by David Orchard.