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.
- Messaging
- Messages
- Application messages
- Formats
- Serialization
- Encodings
- Text
- Binary
- Extensibility
- Extensibility
- Message protocols
- Reliability
- Security
- Extensibility
- Network transports
- HTTP
- TCP
- Named pipes
- Queues
- Extensibility
- Delivery failure
- Basics
of Failure - Fault messages
- Sending faults
- Receiving faults
- Basics
- Messages
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 serviceAnonymous
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.