After months of having my XBOX hooked up on my big screen TV but far away from my cable modem, I finally broke down and bought a wireless adapter for it. I had been thinking about wiring the house and/or buying a Media Center PC. However, Media Center doesn’t support HD inputs (AFAIK) and HD PVR via cable or satellite should be here shortly. So I decided to skip the wiring job and go straight to playtime.

My gamertag is “RayTracer”. (Buy me a beer at the next MSFT conference and I’ll tell you why.) Many thanks to Cory for hooking me up with a gamertag graphic to live on my home page.

Let me know if you want to hit the ice, the mountain, the streets or the sky.

Michael Earls is pleading with MS bloggers to focus on released bits instead of all the cool future stuff we previewed @ PDC. He is especially frustrated with my response to Scoble’s post about how syndication will look in the Longhorn timeframe. Mike, I can’t speak for Scoble or any of the other MS bloggers, but I’m sorry that it’s been hard to keep up. You’re a member of my target audience, so it’s good to know where we are missing the mark.

In my post, I said that Scoble shouldn’t focus on how syndication evolves in the Longhorn timeframe, rather how it evolves in the face of Service Oriented Architecture. And as watered down and nebulous as the term SOA is, when I use it I’m not implying that you have to wait for Longhorn. Indigo will be a great platform for services, but that doesn’t mean you can’t do them today. In fact, the advice coming out of my group is to start doing services right away. Check out the first two sessions from the PDC Architecture Symposium (here and here). In 110 slides there are only about three slides that mention Longhorn, Indigo or Yukon. The rest of the slides are focused on “Practical Advice for Building Your Services Now” (PPT deck from first session, slide 5). Stuff that you gotta worry about regardless of the infrastructure you’re building on. Tentative Operations. Avoiding Ambiguity in Messages. Stability of Data and MetaData. Service Masters and Service Agents. Mike, when you get a chance, please check out those sessions from the PDC Architecture Symposium and then let me know if they can help you right now.

It’s too bad the chapter on SOA that’s posted on MSDN is from a book on Longhorn. That implies you can’t do one without the other. Truth is, you can build traditional tightly coupled apps with Longhorn and, more importantly, you can build services without Longhorn.

What’s weird is that I’m actually not dogfooding anything right now. Oh, I have a VPC with the PDC Longhorn bits and another with Yukon and Whidbey installed, but I haven’t spent much time with them recently. I guess I didn’t make it clear in my recent post on SQL Service Broker that I can’t wait for it because I’m not actually using it yet. The only beta software I’m running on my host machine is Firebird and Thunderbird. I have two primary development VPC’s – XP and WS03 – and the only beta stuff running in either is WSE 2. Call me a slacker, but Whidbey/Yukon/Longhorn aren’t far enough along yet for my current projects.

And I mean you love cheese. As in you rate cheese and say things to co-workers like “this is one of my top 15 cheeses in the world”. You’ve got to check out The American Cheese Society and their annual conference and award winners. They judged over 600 cheeses in 70 categories such as “Fresh Unripened Hispanic and Portuguese Style” and “Sheep’s Milk Washed Rind”.

Too bad they didn’t judge any Venezuelan Beaver Cheese.

While checking out the list of projects hosted at the Rotor Community site, I stumbled across an implementation for Rotor of  Whitespace “a programming language whose syntax is entirely based on space (0×20) tab (0×09) and (0x0A) linefeed”. Seriously.

BTW, the other projects on the Rotor community are much more useful. Check them out.

So I want to start kicking the P2P SDK around again. However, most of my work to date is on my busted laptop that I am still waiting to get fixed. Rather than reinvent the wheel, I started looking at wrapping two other relevant SDKs: IP Helper and Internet Connection Sharing & Firewall. IP Helper allows access to the network configuration of the local computer (including IPv6 settings). ICS/F allows you to programmatically manage XP’s NAT and firewall functionallity (including the IPv6 firewall). Both are relevant to P2P due to the management of IPv6.

I’m not sure why these systems have a custom API instead of just using WMI, but they do. So I’m looking to wrap them either in managed code or WMI (which is then available to managed code via System.Management).

UPDATE: MSFT just published a document about the new Windows Firewall in XP SP2. One of the big new features is the ability to configure the firewall at the global scope., though you can still specify connection settings which override the global settings. SP2 also includes the IPv6 firewall that is a part of the Advanced Networking Pack (which may mean that the P2P infrastructure is baked into SP2). I’m sure this will imply changes to the ICF API.

UPDATE 2: I finally got my laptop back today, and I found my previous P2P work. I hope to kick some code around over the holidays.