SgDotNet
Singapore Professional .NET User Group -For Cool Developers

A mind map for Windows Communication Foundation

I spent some time in space walking various communication technologies for comparisons. They aren't really new, not so "on the center of the cutting edge" (I know you have seen this phrase!)

The below is generated from FreeMind. By the way, FreeMind is a terrific tool for brainstorming or knowledge consolidation, or even sales demonstration. I would love to see any Flickred mind map sharing site, or perhaps in future Google Docs?

Hope the below is useful for situation requiring at-a-glance or quick recall.

WCF

  • Endpoint (ABC)
    • Address
    • Binding
      • Transport Protocol
        • HTTP
        • TCP
        • Named Pipe
        • MSMQ
        • P2P
      • Message Encoding
        • SOAP, Text
        • Binary
        • MTOM (Message Transport Optimization Mechanism) - optimised for large binary payload
      • Communication Pattern
        • Datagram (fire and forget)
      • Reliability
        • Reliable Messaging
      • Security
        • Transport Level
        • Message Level
      • Transaction Propagation
        • Atomic Transactions
      • Interoperability
        • WS-*
        • raw MSMQ message
        • basic Web Service
    • Contract
      • Data Contract
      • Message Contract
      • Fault Contract
  • Comm Layer
    • Intra-Process
    • Inter-Process, same machine
    • Inter-Process, across wire
  • Hosting
    • IIS
      • HTTP transport only
    • Self Hosting
      • ServiceHost(typeof(ABCService), uriBaseAddress) (per transport protocol)
        • ServiceHost.Open
        • Service.Close
      • a physical process to host it
        • process boundary
        • machine boundary
  • Communication over Wire illustrated
    • Client
      • Proxy
        • Channel(s) pipe
          from client -> service pre-processing
          from service -> client post-processing
          • Transport Channel
            • ... Wire ...
              • Transport Channel
                • Channel(s) pipe
                  from client -> service pre-processing
                  from service -> client post-processing
                  • Dispatcher
                    • Business Endpoint
                      • User Code
                  • Message pre-decoding post-encoding
                    • bindary
                    • text
                    • MTOM
                  • set security context
                  • propagate client transaction
                  • manage reliable session
                  • pre-decryption post-encryption
          • Message encoding pre-encoding post-decoding
            • bindary
            • text
            • MTOM
          • set security context
          • propagate client transaction
          • manage reliable session
          • pre-encryption post-encryption
  • Scenario
    • Intermediary Router
    • Federation
    • List-based Publish Subscribe
    • Trusted Facade Service
    • Discovery
    • Peer Channel Custom Peer Resolver
    • REST and POX (Plain Old Xml)

Posted Oct 03 2007, 09:50 AM by blackinkbottle

Comments

BlackInkBottle's Ink wrote Another mind map on Integration Topology (Message Broker, Message Bus etc)
on 10-03-2007 11:24 AM

Theearlier post of mind map focused on WCF. The below is more on integration topology, withmore contents

Copyright SgDotNet 2004-2008
Powered by Community Server (Commercial Edition), by Telligent Systems