I don't usually do a summary post like this one but as I try to go through my ~2000 unread blog posts, I am making a note of those I find interesting.
- It's nice to see that Steve's work is causing a reaction 🙂
- Dennis Pilarinos' blog is one to watch. I have been working with Windows Workflow Foundation (WF) a lot the last few weeks and I really like it. Granted, Chris Sells and I have hit some walls here and there but the WF guys have been great in helping us overcome our problems. Thanks for all your help Dennis! Thanks to Pravin Indurkar and Marcelo Uemura as well for their time to discuss WF state machine futures. (BTW... you may have noticed that I am using the acronym "WF" instead of "WWF". Here's why.). I am also interacting with Dave Green and learning lots!
- BackRow: A "port" of Apple's FrontRow using WinFX. Cool.
- WS-SX. Cooool!
- Aaron Skonnard does an HTTP.SYS transport for WSE 3.0. Way cool. BTW... WSE 3.0 ships on Monday.
- I sympathize with some of Wesner's comments. Not because of my current experience within Microsoft (it's too early to judge) but because I have found that going through the PhD process you do get to think more abstractly, you do get to approach problems in a more systematic manner. Nothing to do with the degree, just the learning process. Paul taught me a lot! So far, however, the people I have been interacting within the company are extremely bright and technically very capable.
- Wow! These xbox 360 videos look fantastic! I don't think I am going to install cable TV in my new apartment by I am definitely getting an xbox 360 (and for that I need an HDTV:-), when I can order the console that is (in the area you can't even pre-order).
- May be of interest: XML Schema Patterns for Databinding Working Group.
- You have to love techies: Clemens and his TV adventures with WCF (there is a follow on as well).
- Dion is "kicking the tires" of SSDL. I am looking forward to the outcome of his investigation (whatever that might be:-) even though the example Dion is using does not highlight all the benefits of SSDL over WSDL. On the subject of SSDL, Simon, Jim and I have been busy with writing an invited chapter for an upcoming "e-Science and workflows" (not the actual title) describing the SC SSDL protocol framework. I am thinking of doing some work on combining Windows Workflow Foundation state machines and SSDL (oh, where's that free time? 🙂
- LINQ resources (via Dion)
- I am with you Don Demsak 🙂 We should concentrate on messages and not expose boundable data/state through endpoints!
- "Contract-first Web Services" by Steve Close (via Eric Newcomer). Of course the 'contract' can be a C# interface, SSDL, or your favourite contract language.
- Hey Robert, sorry it has taken me so long to reply. It was really nice to meet you too. XEST, eh? 🙂 I am looking forward to reading your ideas. BTW... The paper is probably going to be a book now that Jim and I will be starting shortly. I am very excited about it. Also, apologies to Dan for not meeting him at the CodeCamp. I went on Saturday but then I had to spend Sunday looking for an apartment (I wasn't very successful that Sunday). Hmmm... I haven't written about the CodeCamp, have I?
- The Singularity paper is in my reading list.
- "Hypermedia vs Choreography" (via Mark Baker). The thing with MEST/SSDL is that the message behaviour is advertised by the service. The other services wanting to interact with that service can determine whether they can do so or no. There is no "client-side coupling".
- Excuse me? This is sooooo not SOAP! SOAP != HTTP POST and also SOAP != RPC. I didn't expect Mark to agree with this statement.
- "Peek / Poke vs. SPROC" - Jeffrey Schlimmer.
- "The Case Against BPEL" - David Chappel
- "Integration and Interoperability", "Architecture and Architects", "Architecture type definitions" - Michael Platt
- A very nice intro to MSH.
- "Why Just GET and POST?" - Mark Nottingham
- Emerging technology trends
- Food for thought: "Trouble with OSS: Some things that many people ignore" - William Tay
- Hmmm... nice (but I need to think about this some more): "Objects, Components, Web Services" (although it should have been just 'Services') - Also, "10 statements about SOA" - Stefan Tilkov
- This reminded me... I really enjoyed Ted's sessions at the Seattle Seattle CodeCamp.
- "Service Oriented Weakness" - Udi Dahan. Udi makes a good point. However, I will point out that just because marketictets (marketing + architects 🙂 misuse the term to promote their products that's not a failing of the architecture. A set of architectural principles is strong when applied correctly (whether it's called REST, MEST, SOA, OO, etc.). And yes, you can have a service that happens to present a GUI to humans. BTW... I am looking forward to reading about the MEST infrastructure.
- Ha ha ha! Very funny! "WS-Stardate 2005.10" - Tim Bray
- Great interview with my boss 🙂
Phew... that was it! ~2000 blog posts marked as 'read'. Most probably I missed a lot of good ones 🙁 To all bloggers... can you, please, stop blogging for a while? (just joking :-)))
4 responses to “From the blogosphere”
Regarding the echo service, I don’t think I said SOAP == RPC . I certainly don’t think it is. Regarding SOAP != HTTP POST, tell me more about that. Are you saying SOAP can use other transports? What’s the magic I’m missing?
Hey Tony,
Yes, SOAP can be used with other transports as well. There is nothing specific to SOAP to couple it with HTTP. It’s just happens that the only binding that has been standardised (and the most popular one) is the SOAP over HTTP. However, MS, Axis, and probably others are building SOAP over TCP and other transports as well.
SOAP is a message transfer protocol. It treats HTTP as a transport protocol (and not as an application protocol).
Does this make sense? Feel free to email me if you want to chat about this.
.savas.
Hi Savas,
I asked the question badly. I realize SOAP can be sent over the transport of your choice, but in the case of HTTP, what is the issue with an exchange of documents as I’ve described it? A service accepts a document and returns a document. That is exactly what a SOAP service is. The returned document can be a static document. A Web server can return a static document. Why is that not SOAP?
That is indeed one way of serving a SOAP message but it has nothing to do with SOAP, the spec. Also, SOAP says nothing about request-response which is what you are describing here. If what you are describing does not violate the SOAP/HTTP binding, then that’s fine. However, please note that the SOAP spec is completely agnostic to all these, hence my comment.