Due to a temporary reassignment this morning, I spent my usual blogging time moving all of my computer equipment from one cube to another.

• Sam Gentile writes about the ALT.NET moniker. My favorite of his principles is number 4 where he discusses the importance of tools versus principles and knowledge. I really agree that knowledge and principles are more important because the best tools in the world can’t help us if we don’t know how and when to use them.
• I find Mark Cuban’s ideas (here and here) about how advertising on the Internet is different than traditional media advertising. He points out that the ability of a provider to deliver higher simultaneous views is more important and valuable than delivering views for a longer period of time. I think he right on here, even if I believe his football league is going to fail. (via Blog Maverick)
• Worse Than Failure has been running an unusual contest to get the most interesting, buggy, and unusual way of writing a calculator application. They have 12 finalists for readers to review. I find that the descriptions of how the programs work (or don’t) to be hilarious.
• As I have been working on service-oriented management and monitoring I have given a lot of thought to the best way to present the data. Doesn’t it make the most sense to primarily display information from the business process point of view? I would be interested in your feedback.

Since there appears to be at least a handful of RESTifarians among my readership, I’m just going to throw this half-formed thought / almost question out there. Maybe it’s a FAQ, in which case I’d appreciate a pointer in the right direction.

My observations about REST are:

1. REST is a an “architectural style for distributed hypermedia systems“.
2. REST “has been used to guide the design and development” of HTTP and URI.
3. Therefore REST as an architectural style is independent of HTTP and URI.
4. Yet, I get the feeling that the REST community would consider a solution that uses the REST architectural style but not HTTP and/or URI as “not RESTful”.

Am I wrong in observation #4 above? If you’re addressing resources by resource identifiers [aka URIs] but transferring those resource representations over a durable duplex protocol [aka not HTTP], are you still RESTing?

(Note, such a RESTful durable duplex protocol doesn’t exist to my knowledge, though I would be very happy to be wrong about that. SSB does durable duplex, but it doesn’t support URI style resource addressing. Granted, if I was going to build a durable duplex RESTful protocol, I would build on SSB – much the same way that HTTP builds on TCP. Though I am a huge fan of SSB, I’m specifically not suggesting that SSB is RESTful.)

My session yesterday went very well, especially considering I did no prep whatsoever. Drew a fairly good sized audience – people were sitting on the floor and standing in the back, though honestly the TLC “theaters” only hold about 50 chairs. Most of them stayed the for whole session – at least until I started to run over (only 15 minutes, not too bad).

After my session, I ended up talking to a customer from a large home loan firm for about two hours. Turns out we had a friend in common, a guy I used to work with a long time ago @ ModaCad named Brian. This is actually the second time I’ve run into someone at a major Microsoft conference who has a single degree of Brian, which is a little freaky.

For dinner, I went out with some MS field architects and some customers. We ended up having such a big group, we split up into two tables and somehow my table had four MS employees and only one customer. But that customer was from a very large retail firm and we had lots to talk about. Ate way too much, though I didn’t combine that with drinking too much. And, as a bonus, I didn’t tell the customer than any of their ideas were “stupid”, as my friend Christoph pointed out I had done the last time I was out to dinner with one of his customers. (That customer wanted to run Java on their mainframe. I stand by my assessment.)

I was planning to head up to my room, but ran into Jon Flanders in the lobby. Hadn’t seen Jon since the class I took with him last fall, so I ended up hanging out with him for several hours, chatting up the folks we knew who walked by, including Rocky, Bob and Brian. I realized I’ve been heads down with no speaking or travel for about a year, so it’s been a while since I had seen many of these folks. For example, I hadn’t seen Brian in about three years when we were both presenting at TechEd New Zealand. The downside of hanging out in the lobby is that I didn’t get any code written last night, which I was sort of planning to do when I headed back to the hotel. But chatting with these folks – esp. Jon this time – helps be figure out what I want to write anyway, so I guess it’s worth it! 😄

I ended up sleeping in this morning (still jet lagged) and skipping the morning session. No second keynote this year, which I didn’t realize until I looked at the conf guide this morning. Not sure if that’s a good thing or a bad thing.