Поделиться через


Table of Contents Scratch Work

I haven't forgotten about the goal to put together a table of contents for all of these articles. The part I find hardest about this process is taking the articles that talk about five or six topics and figuring out a single place where they should go. I want to avoid duplicating and cross-linking articles at this level. Here's an example of the products I'm coming up with along the way. I've populated this list with just the articles tagged as involving "messages". That's about 10% of the total number of articles. It takes a long time to get a working organization and design.

  1. Messaging
    1. Messages
      1. Application messages
        1. Reducing
          Memory Usage with Large Messages
        2. Mixing
          Message Contract Attributes
        3. Splitting
          Up XML Text Nodes
        4. Correlating
          Message Identifiers
        5. You
          Must Understand This
        6. This
          message cannot support the operation because it has been copied
        7. Maximum
          Size of a SOAP Message
      2. Formats
        1. Versioning
          for Addresses, Envelopes, and Messages
        2. Manual
          Addressing
        3. Mixed
          Mode Addressing
        4. The
          Mixed Mode Addressing Picture
      3. Serialization
        1. Using
          XML Serialization with WCF
      4. Encodings
        1. Text
        2. Binary
        3. Extensibility
      5. Extensibility
        1. Get
          the Message
        2. Introducing
          MessageState
    2. Message protocols
      1. Reliability
      2. Security
        1. Securing
          Custom Headers, Version 1
        2. Securing
          Custom Headers, Version 2
      3. Extensibility
    3. Network transports
      1. HTTP
        1. Making
          One-Way HTTP Requests, Part 2
        2. Making
          One-Way HTTP Requests, Part 3
        3. Status codes
          1. Modifying
            HTTP Error Codes, Part 1
          2. Modifying
            HTTP Error Codes, Part 2
          3. Faults
            and HTTP
      2. TCP
      3. Named pipes
      4. Queues
      5. Extensibility
    4. Delivery failure
      1. Basics
        of Failure
      2. Fault messages
        1. Actions
          for FaultExceptions
        2. A
          Historical, Awkwardly Named Fault
        3. The
          Most Distinguished Fault
      3. Sending faults
        1. Designing
          New Faults
        2. Creating
          Faults, Part 1
        3. Creating
          Faults, Part 2
        4. Creating
          Faults, Part 3
      4. Receiving faults
        1. Zen
          Faults
        2. Consuming
          Faults, Part 1
        3. Consuming
          Faults, Part 2

Next time: Channel Development Tour, Part 1

Comments

  • Anonymous
    February 16, 2007
    A table of contents is an excellent idea. It would also be cool if you could find a book publisher for all of your hard work, I for one would be first inline to purchase this great content in hardcover as well.

  • Anonymous
    February 16, 2007
    How do I store some state about the current request so that I can use it later during the same service

  • Anonymous
    February 18, 2007
    Great work!

  • Anonymous
    February 18, 2007
    Finding a publisher is less of a problem than finding time to write a book.  I've gotten several offers already but it's hard to fit it into my schedule.