All posts by : steve maines blog

1 of 135 | Cool open source WCF tool - Eyal Vardi has been coding up a storm, it seems. He's got a lot of neat tools for WCF/.NET development up on his weblog. My favorites are the WCF Debugger Visualizers. The internal structure of some of the WCF runtime objects (like ServiceHost and ServiceDescription) can get quite complicated, and spelunking those through the tiny window provided by the debugger's default property grid can be painful. Once you install Eyal's visualizers, you get a rich visual view that makes exploring the OM much easier. The code is up on CodePlex: WCFVisualizer Thanks Eyal! ...

2 of 135 | We are pleased to bring you new features in .NET 3.5 SP1 - In case you haven't noticed yet, the bits for .NET 3.5 SP1 Beta 1 and Visual Studio 2008  SP1 Beta 1 are now available...take a minute and go grab them, and then you can finish reading this post while they install :) What's new? Looking at the platform holistically, the big-ticket features in SP1 are the ADO.NET Entity Framework (finally ;) ) and the ADO.NET Data Services (Astoria). I'm sure lots of folks will be talking in-depth about those things, so I'll focus on some of the smaller (but no less interesting!) features that my team is delivering as part of this release. From the WCF/WF perspective, here's what you can look for in SP1. There's a lot here and each o......

3 of 135 | Read Brian's blog on F# - You should seriously check out Brian's F# blog. It's way good. Brian is a WCF alum; he owned a hefty chunk of the code in System.ServiceModel.Dispatcher and the 3.5 Web Programming Model work. It's funny...I used to mistype his name in emails a "Brain McNamara" at least once a week, which actually was a pretty accurate statement. Anyway, he's over in 41 working on the F# compiler now and blogging up a storm. I'm spending more time getting to know the F# language, and I'm liking what I'm seeing. ...

4 of 135 | Partial trust binding validation is a usability feature - Nicholas has a good post on the binding validation WCF does in partial trust. As he points out, a ServiceHost running in anything less than a fully trusted AppDomin will so some baked-in validation on the bindings being used. Specifically, we have a list of binding elements that are explicitly prohibited in partial trust, and if we catch you trying to use one of these binding elements we'll prevent your service from activating. This behavior has absolutely nothing (zip, zero, nada) to do with security. For that, we rely on the Code Access Security features implemented by the CLR, like any other framework component. So why do we do this validation? One reason -- usabi......

5 of 135 | WCF Web Programming Model Documentation - I've gotten a lot of requests (internally and externally) for requests for resources on how to use the new WCF Web Programming Model features in .NET 3.5. MSDN has a lot of great content on this stuff, but it's kind of sprinkled around in various places due to the way the MSDN table of contents is laid out. I figured it would be nice to have links to all of the important topics in one place, so here's the "mini-TOC" for the Web Programming Model content: Conceptual Overviews: Web Programming Model AJAX and JSON WCF Syndication (Atom and RSS) Partial Trust Class Library Reference (not exhaustive): System.ServiceModel.Web Namespace Syste......

6 of 135 | Declaring XML Namespaces on a SyndicationFeed - Lots of folks have asked me how to add various XMLism like XML Namespace prefixes to the serialized output of a SyndicationFeed. This is actually easy to do once you know the trick but it's admittedly not the most obvious thing in the world. The thing to remember is that the System.Xml stack treats prefix declarations as special kinds of attributes. If you want to emit an XML namespace declaration of xmlns:contoso=http://schemas.contoso.com you need to emit attribute whose name is the prefix you're declaring (e.g. "contoso"), whose value is the namespace URI that corresponds to the prefix (e.g. 'http://schemas.contoso.com'). This attribute needs to be in the special XML namesp......

7 of 135 | ContractNamespaceAttribute and Serialization - One of the things that the DataContractSerializer does is create a mapping between CLR type names and XML qnames. Lots of people know that you can control this mapping on a per-type basis via the [DataContract] attribute, e.g. namespace Contoso.Serialization {   [DataContract( Namespace="http://schemas.contoso.com/2008" )]   public class Person   {      [DataMember]      public string Name { get; set; }   } } Having to explicitly specify this on every type gets a little laborious, especially if you just want to say "put all types in this CLR namespace into this XML namespace". Few people know th......

8 of 135 | Wisdom from Ganesh - I thought this post from Ganesh Prasad was both cheeky and refreshing: Though I like REST and consider it a very elegant model for SOA, it's a little tiresome to hear day in and day out that it's so much more elegant than the SOAP-based Web Services model. In fact, I'm getting so tired of this shrill posturing that I'm going to stick it to the RESTafarians right now, in their own style. Watch. Paying the RESTafarians Back in Their Own Coin I think I would get along well with Ganesh. ...

9 of 135 | Update from TechEd - Day Three of TechEd Orlando is pretty much in the books -- newsflash: when it rains down here, it really rains. I've spent most of my time here hanging out in the SOA + Web Services area of the Technical Learning Center. For those of you at Tech Ed, it's the blue one. I'll be there tomorrow as well, so if you have a question about WCF or just want to talk about the web you should come on by. Tomorrow, my good friends Ed Pinto and Kenny Wolf will be doing a 400-level talk on WCF Architecture and Extensibility. This is the talk to go to if you're interested in exploring WCF from the inside out. It's going to be a great talk; I'll probably......

10 of 135 | Hanselman on Ruby - Scott's got some good comments on the Ruby aesthetic. I find some of the Ruby idioms to be really interesting. Specifically, the attempt to bring programming language closer to the natural language is an admirable goal. That said, I wonder how well they translate and whether this style is ultimately a help or a hindrance to Ruby coders who don't natively speak English (at the very least, it puts a different slant on the globalization problem). And I know Matz is Japanese, but it seems like a lot of this comes in the framework/standard libary. I think Ruby has landed in an interesting place -- it has a nice mix of core lang......

11 of 135 | Zen of the Web Programming Model (Part 3) - The importance of Content-Type One of the amazing things about the web is that it's a vast interconnected graph of heterogeneous data that can be traversed in a generic way. Half of this story is enabled through a uniform interface for moving the bits around -- URI's and HTTP methods. The other half is about uniform formats for entity bodies so systems can process data once it gets to them. One without the other is like a yin without a yang. One of the nice things about the web is that the base mechanism for moving bits around (URI's and HTTP methods) doesn't much care about the format those bits conform to.......

12 of 135 | Zen of the Web Programming Model (part 2) - Part 1 I find that I often get a chuckle out of presenting seemingly obvious information in non-obvious ways. That basic juxtaposition and fundamental element of irony goes a long way towards explaining the inner workings of my somewhat obtuse sense of humor (well, that and fart jokes). Anyway, I think that's what I had rolling around in my head when I creating the following slide about the relative popularity of the various HTTP methods:   The point being, of course, that GET and POST are by far the most common methods on the Web today (Side note -- I wonder how different this graph would be had early versions of HTML&n......

13 of 135 | A Brief Aside: WebServiceHostFactory - Ouch, it looks like Jef ran headlong into a bit of a brick wall using the Web programming model inside of ASP.NET.  That one's my fault for not getting the time to write an ASP.NET sample before the SDK shipped. Had I done that, I could have saved Jef some pain and a long blog post. So Jef, I apologize. I owe you a beer next time I see you. Let me try to make it up to you. The basic gist of Jef's post is that "there's too much *@#%!^ config required to use your stuff!". I agree. That's why we added two types to the Web programming model for making this easier -- System.ServiceModel.Web.WebServiceHost and System.ServiceModel.Web.WebS......

14 of 135 | Zen of the Web Programming Model (Part 1) - In our Mix talk, Don joked about how we were taking off the 'philosoper's robes' when it came to designing this feature set. If you're waiting for the "Four Tenets of REST Orientation" to come out of this work, I think you'll be waiting for quite a while. There are no tenets or orientations here -- just some practical stuff based on what people are doing on the web today. We've made some observations about what people are struggling with on the platform as it is now, identified their pain points, and hopefully given them some aspirin to make their coding lives simpler and more productive. That said, I would get thrown out of CSD if&nb......

15 of 135 | Balancing reach and rich - I've been enjoying reading some of the reactions to our Web Programming Model features -- particularly Jef Newsom's post Some Interesting History and David Ing's Simple Object Apology Protocol. Both make some great points and are well worth the read. Jef writes: So, it is interesting to me to watch guys like Clemens Vasters and Don Box (and Steve Maine, though I think he was less heavily involved in 'expectorating' the WS-splat and a lot more heavily involved in consuming and evangelizing prior to getting into the big house) starting to shed the WS-Splat baggage and just GET it. And I think that they are being pragmatic about it......

16 of 135 | Programmable Web features in the BizTalk Services SDK - First, go download the SDK from http://labs.biztalk.net. Now that you've downloaded it, you've got a whole bunch of new stuff to play with. Let me give you the guided tour of the Programmable Web stuff (the Connectivity and Identity stuff will have to wait for another day). All the assemblies live in the \Assemblies folder underneath root installation directory. If you installed them in the default place, you'll find them in C:\Program Files\BizTalk Services SDK\Assemblies. This is where you can point your Visual Studio "Add Reference" dialog at if you want to build apps on top of this stuff. Inside this folder, you'......

17 of 135 | Mix is done (and our new bits are live) - Phew, Mix is over. The conference technically ended yesterday but we had a follow-on event with a few customers to dive deeper into Web Programming Model stuff that Don and I covered in our Navigating the Programmable Web talk (the recording of which is now live on http://sessions.mix.com). Bottom line is that I'm just now getting some time to blog... I'm really stoked to announce that all the bits that Don and I used in our demo are now available to the public as part of the newly refreshed BizTalk Services SDK, which can be found at http://labs.biztalk.net (webby folks, don't let the BizTalk name scare you -- remember, URI's are opaque ;)......

18 of 135 | Navigating the Programmable Web -- tomorrow @ Mix '07 - Don and I are doing our talk at Mix tomorrow morning -- it's at 10 am (hopefully everyone will be fully recovered from the attendee party by then -- if not, we'll play some soothing music or something...) The talk is titled "Navigating the Programmable Web", but it's really going to be quite the code-fest. We're going to be taking the wrapper off the new WCF programming model features for web-style services tomorrow (the stuff that Mark Baker and others have helped with, which we're quite grateful for), so it should be a really good time. I even learned some XAML for this talk :) Bottom line is that if you've played with the "webby" features......

19 of 135 | Programming Model for HTTP Status Codes - In my last post on HTTP/POX basics, Dave Bettin asked a good question in the comments: Will you guys have a good story around a programming model for associating HTTP status codes with CLR exceptions? Or are we stuck with the existing fault model? The short answer is "of course we'll have a good story around programming HTTP status exceptions!" We haven't landed on whether that model will be based on exceptions or not. Exceptions are a nice control flow abstraction for doing non-local jumps out of a method body (which is sometimes what you want with status codes, but not always). The downside is that they're relatively expensive from a ......

20 of 135 | HTTP/POX Programming Basics - One of the goals we have for WCF in Orcas is to extend our feature set to better meet the needs of the "plain old XML over HTTP programmer". In other words, we're all about making the experience of building these types of apps better on our platform. There's a good chunk of this story already in the March CTP bits, and there will be more coming in Orcas Beta 2. The price of admission for POX Making WCF speak POX involves three things: Washing the SOAP off the binding. Dispatching HTTP requests -> server operations Programming model support at the Service Model layer for controlling the det......

21 of 135 | Orcas and Me - The March CTP of Orcas went out the door this week, which is notable for many reasons. The ones that have the most immediate impact on me and my life are as follows: 1) This is the first real public release my team has shipped since Vista (which is pretty cool, considering that Vista closed down for us about six months ago and Indigo V1 took...much longer than that :) ) 2) This is the first release we've done since we combined the WF and WCF teams under one roof. As of about January, we're now all literally under one roof. The WF team came over to 42, so we're all located physically in the same space. It's much easier to talk to peo......

22 of 135 | Partial Trust support for WCF in Orcas - In order to get WCF out the door on time, we had to make a few really painful cuts. Such things are a necessary part of shipping software, but they're never fun. Setting [AllowPartiallyTrustedCallers] on System.ServiceModel.dll to enable the use WCF in Partial Trust was definitely one of those. Relatively speaking, we made this cut pretty early on in V1 (before WCF Beta 1). Setting APTCA is not something you do lightly, and it was pretty clear that if we ever wanted to test this thing before it went out the door,  we'd have to put Partial Trust on the chopping block. So we screwed up our courage, cut the feature, and......

23 of 135 | Dogs and cats sleeping together!!! - There's lots of buzz in the blogosphere today about the big Cardspace/OpenId collaboration that was announced this morning at RSA. Whodathunk that a technology rooted in the RESTful open source ecosystem could intermingle with a technology built by the WS-* wonks without trigging some bizarre matter/antimatter explosion...next thing you know somebody's going to come up with a tasty combination of chocolate and peanut butter and then it's all down hill from there... Kidding aside, I think today's announcement is really cool. I'm looking forward to seeing more talk about OpenID around CSD (the Connected Systems Division -- which buil......

24 of 135 | Channel 9 and the Indigettes - Rory from Channel 9 stopped by last week and interviewed a few of us Indigo folk. I don't think he got quite what he was expecting, but the results were amusing nonetheless. Check it out. ...

25 of 135 | Indigo -- Shipped! - The RTM release of Windows Communication Foundation (lovingly but heretically referred to as "Indigo" -- some names just stick) went live on MSDN today as part of the .Net Framework 3.0 download[1], which makes this a pretty darn cool day. Go build some apps! Here are links that will help you with that: Microsoft Windows SDK for .NET Framework 3.0 Microsoft Visual Studio 2005 CTP Extensions for .NET Framework 3.0 (WCF & WPF) Microsoft Visual Studio 2005 Extensions for Windows WorkFlow Foundation Enjoy the bits... [1] Vista release Coming Soon, as part of a bit larger redist (one that includes the whole OS......

26 of 135 | Vista -- RTM - See, I told you the Vista release of Indigo would be coming soon... Vista was released to manufacturing today!!! This site has all the details: http://www.microsoft.com/presspass/features/2006/nov06/11-08VistaRTM.mspx ...

27 of 135 | A simple-ish approach to custom context in WCF - In WCF, we have this thing called OperationContext.Current that carries lots of useful information about the 'current' service operation being processed. You can use this on the server to fish out the ServiceEndpoint that the message you're processing came in on. On the client, you can use OperationContext.Current to do things like adding custom headers to the outgoing message. All in all, OperationContext.Current is the place to go for WCF-specific context about the current operation. It's pretty common to want to extend this patten to cover app-specific context as well (see this post on the WCF forums, which inspired me to write this blo......

28 of 135 | RC1 - Today is a very, very cool day. Windows Communication Foundation (the API Formerly Known as Indigo) shipped RC1 to the world. You can get the bits right now. And when we say "release candidate", we mean it. As Clemens says, there are only a "handful" of active issues in the bug database (and you don't need very big hands). The time has come for us to ship, and believe me, I can't wait to get this in the hands of our customers. So go, play with the bits already :) ...

29 of 135 | AddressFilterMode.Prefix - By default, the WCF dispatch runtime will match messages to their destination endpoint using an exact matching algorithm on the message's To: header. This means that if you have a service endpoint listening at http://foo.com/endpoint1/, messages addressed to http://foo.com/endpoint1/somethingElse will return an EndpointNotFound fault. Conceptually, your endpoint is listening on exactly one URI and if the wsa:To header doesn't match that URI, the messages ain't going to get there. However, in fairly recent bits (the July CTP), we introduced the ability to do the following: [ServiceBehavior( AddressFilterMode = AddressFilterMode.Prefix )] ......

30 of 135 | Really, I'm about a 4 on the Tilkov scale - Stefan's putting together sort of a Kinsey Scale for distributed systems bloggers. Odd that he publishes this post (which puts me in the WS-Only camp) on the same weekend I spent writing the REST/POX scenario sample for the WCF SDK... If this debate is really about favoring a proliferation of verbs vs. a proliferation of nouns, service-specific interfaces vs. generalized interfaces or whether the URI identifies the locus of processing vs. the thing being processed, then I personally tend to prefer the latter for all three at the application layer. When I've posted about REST on this blog, I've basically harped on two poin......

31 of 135 | Fiddler 1.2 (now with font sizes!) - I just noticed that Eric Lawrence has released version 1.2 of his fantabulous Fiddler HTTP debugging proxy (get it now at http://www.fiddlertool.com). If you're doing POX/HTTP work (with Indigo or pretty much anything else on Windows), Fiddler is definitely worth having in your toolbox. One nice little addition in Fiddler 1.2 -- you can bump the font size up! This makes Fiddler much more suitable for using in demos and presentations, which is something I've been wanting to for a long time. Thanks Eric! ...

32 of 135 | MessageVersion.None - Kenny has a great writeup of how we rolled SOAP-free XML messaging into the WCF channel/encoder model. The short answer is that we normalized POX messages into our model by defining a special MessageVersion -- MessageVersion.None -- that implies the absence of a SOAP envelope. This enables basic POX support in the channel model and removes the need for all that mucking about with the HttpMappingMode knob on the HttpTransportBindingElement (which, while modestly better than the MapAddressingHeadersToHttpHeaders="true" that we used to have in Beta 1, was quite bogus). Up at the service model layer, the out-of-the-box way of doing POX ......

33 of 135 | ServiceHostFactory vs ServiceHostFactoryBase - Last time around I talked about how the ServiceHostFactory API allows you to use custom derivatives of System.ServiceModel.ServiceHost with the WCF hosting infrastructure that runs in IIS/WAS. If you've been poking around the System.ServiceModel.Activation OM, you might have noticed that we actually have two service-host-factory-ish classes. Specifically, we have System.ServiceModel.Activation.ServiceHostFactory (which was that subject of my last post), as well as its more mysterious abstract base class System.ServiceModel.Activation.ServiceHostFactoryBase (which has yet to be mentioned at all). You might have also noticed that the Ser......

34 of 135 | Of Hosts and Factories - I promised in my last post on the @ServiceHost Directive that I would talk in more detail about Factory attribute in that directive and why we have it. So here goes… The motivation for API’s that I’m going to talk about in this post stems from the fact that the standard API for hosting services in WCF (System.ServiceModel.ServiceHost) is a first-class extensibility point in the WCF architecture. We expect that lots of folks will derive their own host classes from ServiceHost, usually with the intent of overriding ServiceHost.OnOpening in order to do interesting things with the ServiceDescription (e.g. adding default endpoints imperatively, or......

35 of 135 | The @ServiceHost Directive - One of the most common exceptions people seem to run into when building IIS/WAS-hosted WCF services is the dreaded Parse Error: The unknown directive @Service was specified. This is caused by a syntactic change we made during the latter part of the development cycle (I think it went in between WCF Beta2 and WCF RC0, but my memory is hazy). The new directive is names @ServiceHost, and it usually looks like this: <% @ServiceHost Service=”MyService,MyNamespace” %> That’s the simplest possible form of the @ServiceHost directive. There are other attributes you can specify (such as Language and CodeBehind) which govern how any code yo......

36 of 135 | Code from my TechEd talk - Here is the code that I presented in my TechEd talk (CON 325 -- WCF for ASP.NET Developers) HostingInAspNet.zip (343.83 KB) CompatibilityMode.zip (351.16 KB) Pox1.zip (187.28 KB) These are all built against WCF Beta 2. I'm out for the next few days on vacation. Thanks everyone for a great TechEd '06! ...

37 of 135 | WCF RSS Toolkit - More goodness up on http://wcf.netfx3.com: the WCF RSS Toolkit is up! You can download the source from here. Practically speaking, this toolkit gives you a framework for easily exposing your server-side data as RSS 2.0 or Atom 1.0 feeds. If you have some data somewhere (in a object graph, a SQL query, or anything that you can slap [DataContract]/[DataMember] on), you can use this framework to syndicate that data to the outside world. The model here is that an RSS feed is just an interesting type of WCF service. It exposes endpoints, and those endpoints have the {Address, Binding, Contract} characteristics of any other service. There are......

38 of 135 | wcf.netfx3.com - Check it out: the Indigo WCF community's new home on the web is http://wcf.netfx3.com. The "hello, world" post from Clemens has the scoop. There's already some great stuff up there, and more will be coming soon...including the WCF RSS Toolkit...stay tuned... If you've got a WCF sample that you'd like to contribute, the details can be found here. Fame and glory await!* *fame and/or glory not necessarily guaranteed ...

39 of 135 | Off to TechEd - I'm heading out this afternoon for TechEd 2006 in Boston. My big talk is on Wednesday. It's a 300-level talk that deals with how WCF fits in with ASP.NET:   CON325  (WinFX) Windows Communication Foundation: WCF for ASP.NET Developers Day/Time: Wednesday, June 14 3:45 PM - 5:00 PM  Room: 107 ABC Speaker(s): Steve Maine Are you an ASP.NET developer looking to build the next generation of Web applications? If so, then come and see how the Windows Communication Foundation integrates with today's ASP.NET applications and can help you build tomorrow's Web-based appli......

40 of 135 | Blogging from Office 12 - If you’re reading this, I’ve managed to get DasBlog’s XML-RPC infrastructure to work with Office 12 DateTime format. I wonder if the HTML conversion handles emphasis, italics, and fonts decently. Looks like it does. Now all I need is a decent “code” style and I’ll be quite happy. Too bad categories don’t work for MetaWeblog in Beta 2. I’ll live, though ...

41 of 135 | Lost questions - I apologize for the lack of technical content on this blog lately. We've all been pretty heads-down lately, getting this whole WCF thing in the landing pattern for V1. We're at the stage where it's just about time to make sure all the seatbacks and tray tables are in their full upright and locked position and the "fasten seatbelt" sign has recently been turned on (as it were). Doesn't leave much time for blogging. Anyway, here are some musings about one of my non-technical obsessions: Lost. The finale for Season 2 is next week, and if you haven't been watching you should stop now, because I'd hate to spoil the fun for you. But here are some interest......

42 of 135 | WS-Addressing goes Full Rec - WS-Addressing is now a full W3C Recommendation! Congrats to the working group (especially the MS crew of Gudge, Jonathan Marsh, Marc Goodner, and Mike Vernal) for getting this puppy out the door. ...

43 of 135 | A brief tour of service activation - I wrote this up in response to a question on an internal list about what the service activation path looks like in hosted environments such as IIS or WAS. Thought it might be useful to a wider audience. The story starts just after the request has been dispatched to the worker process, but before pretty much anything else has run. We now join the following thought process already in progress:   ...We have a piece of infrastructure (an HttpModule for the HTTP case, a new thing called a ProtocolHandler for the non-HTTP case in WAS) that receives Indigo requests and stuffs them into a holding area while the transport stack comes up. The ......

44 of 135 | Checkin #1383521 - Thanks to the hard work of several people (particularly Kenny), the Indigo world is now a better place for everyone. It will be a while before these changes are publicly available, but at least you know what's coming down the pipe: From: Indigo SNAP Lab Account Sent: Wednesday, April 12, 2006 1:05 PM To: Indigo Checkin Alias Cc: Kenny Wolf Subject: indigo_wap checkin 1383521: kennyw: DCR#50761: Add support for POX messages to TextEncoder   > INDIGO_WAP Checkin 1383521 CHANGE: ......

45 of 135 | Great article about ClickOnce and WCF - I get asked fairly frequently if ClickOnce and WCF are mutually exclusive. Lots of folks seem to be under the impression that you can't use WCF in a ClickOnce application because of our requirement for Full Trust permissions -- which is a misnomer. Truth is, Indigo works fine in a ClickOnce app. Check out this article by Matias Woloski which really nicely documents the whole process. ...

46 of 135 | I see why people dig JSON - JSON and XML-RPC: {     "lowerBound" : 18,     "upperBound": 139 } vs. <struct>    <member>       <name>lowerBound</name>       <value><i4>18</i4></value>    </member>    <member>       <name>upperBound</name>       <value><i4>139</i4></value>    </member> </struct> Yay for isomorphism. ...

47 of 135 | Subtle Distinctions (drawing the line between REST and POX) - A thought experiment on line between REST and POX... Let's say there's an app that exposes domain-specific XML data via HTTP GET endpoints. That is, I can get back an XML document describing some application-specific entity by issuing HTTP GET's to URI's like the following:     http://foo.com/CustomerProcessor.aspx?methodName=GetCustomer&customerId=12     http://foo.com/CustomerProcessor.aspx?methodName=GetCustomerDetails&customerID=12 This is a pretty typical of many POX/Lo-REST applications out there. Question is, is this application also RESTful in the Fielding sense? Where do we draw the line? ......

48 of 135 | Lo-REST Round-Up - Dare: Don's definitions can probably be altered a little to become Lo-Rest, which is the use of HTTP GET (or equiv) for information retrieval/query and POST for everything else, and Hi-Rest, which is characterized by the use of distinct HTTP methods to perform distinct operations on resources, for example using HTTP PUT and DELETE (or equiv) for doing update. This definition draws a distinction between REST as it is practiced on the Web today (i.e. Lo-REST) and REST as it should be practiced on the Web today (i.e. Hi-REST). A couple of other folks also disagreed with Don's definitions. They include Jonnay in his post ......

49 of 135 | atlas + indigo = crazy delicious - We announced a new drop of Atlas at Mix today. Now you get to know why it's been so quiet around this blog lately: http://atlas.asp.net/docs/atlas/doc/wcf/default.aspx This release of Atlas ships with some WCF extensions that let Atlas browser clients seamlessly communicate with WCF services -- no SOAP required ;)   ...

50 of 135 | Mix '06 - I'm heading out tomorrow night for Mix '06. If you want to talk about POX, REST, RSS, AJAX, Indigo, or whatever, I'll be spending a lot of my time hanging out in the Sandbox. I won't quite have Phil Haacks' eye-burning aloha shirt, but hopefully I'll be easy to find. This should be fun. I haven't gone to a conference with the sole purpose of having conversations with customers and getting a feel for their issues in a really long time. I'm sure it will be educational. See you there. ...