Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The OSOA reference binding list was used to represent resolved/configured bindings which meant editing breaking the model as read from XML.to resolve references
  2. OASIS have a different approach to matching references/service so factoring our out endpoint references/enpoints from refefencesreferences/services will allow a switchable algorithm to be deployed
  3. New policy model can use endpoint models as policy subjects
  4. Support late reference resolution

Scenarios

  1. Static domain - where all composites are present before nodes are started
    • as now composites will automatically be configured with unwired bindings
  2. Incremental deployment - where nodes are started with composites before the domain is complete
    • Endpoint logic will ask the domain for information required to resolve endpoint references with endpoints
  3. Service Location Transparency - a future scenario where nodes can be moved
    • Endpoint/binding logic can again be used to ask the domain for new endpoint information
    • Am in two minds about this one, do we Could just let each binding handle it or do we get but maybe some advantage to having the enpoint reference to handle it by stopping/reconfiguring/starting the binding
  4. Dynamic Domain - in the future but some scenarios call for components to be reconfigured at runtime
    • Endpoint reference and endpoint concepts focus the effort of adding removing wires

Overview

Model

Activation

...

Creation and Activation

  • Create
    • Endpoint reference and endpoint models are created at build time
  • Activate
    • Create the endpoint wires
    • Create the endpoint reference wires (eventual target service may not be known)
  • Start
    • Start bindings
  • Invoke
    • Endpoint - create chains when first message arrives
    • Endpoint reference
      • If endpoint resolved go ahead and created chains
      • If endpoint not resolved try and resolve it and then create chanings
  • ServiceUnavailable at endpoint reference
    • repeat the endpoint reference resolution step
  • Resolve
    • There is a separate phase that resolves endpoint references to endpoints in the domain this can be run at build time but may be required later also