http://blogs.msdn.com/drnick/archive/2007/01/05/designing-new-faults.aspxThe last piece of this eleven part series on fault messages covers advice for channel authors that need to define their own set of faults. Everything here assumes that you're writing a protocol channel, that you have interesting failure cases that needenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/drnick/archive/2007/01/05/designing-new-faults.aspx#1417369Fri, 05 Jan 2007 21:25:19 GMT91d46819-8472-40ad-a661-2c78acb4018c:1417369Nicholas Allen's Indigo Blog : Faults and HTTP<p>PingBack from <a rel="nofollow" target="_new" href="http://blogs.msdn.com/drnick/archive/2007/01/04/faults-and-http.aspx">http://blogs.msdn.com/drnick/archive/2007/01/04/faults-and-http.aspx</a></p> http://blogs.msdn.com/drnick/archive/2007/01/05/designing-new-faults.aspx#1420564Sat, 06 Jan 2007 07:08:23 GMT91d46819-8472-40ad-a661-2c78acb4018c:1420564Jason Haleyhttp://blogs.msdn.com/drnick/archive/2007/01/05/designing-new-faults.aspx#1445467Wed, 10 Jan 2007 21:47:41 GMT91d46819-8472-40ad-a661-2c78acb4018c:1445467Sam Gentile<p>Completely buried with two projects and the main one is going to CTP #2 at a major back in Paris/London</p> http://blogs.msdn.com/drnick/archive/2007/01/05/designing-new-faults.aspx#1522688Wed, 24 Jan 2007 20:38:07 GMT91d46819-8472-40ad-a661-2c78acb4018c:1522688Nicholas Allen's Indigo Blog<p>Back to errors and faults for a bit with this two part series on modifying the HTTP status code used</p> http://blogs.msdn.com/drnick/archive/2007/01/05/designing-new-faults.aspx#1717867Mon, 19 Feb 2007 21:46:59 GMT91d46819-8472-40ad-a661-2c78acb4018c:1717867Nicholas Allen's Indigo Blog<p>I haven't forgotten about the goal to put together a table of contents for all of these articles. The</p>