Home
Enabling ESL Interoperability

info@greensocs.com

  • Products and Services
  • Downloads
  • Documentation
  • Projects
  • Support
  • About Us
Projects / GreenBus / History of GreenBus / Design / PortPort

Green Bus

  • You must register/login in order to post into this group.

PortPort

History of GreenBus

  • Changes
  • CopyAtSlave
  • Design
    • addressType
    • byteLabe
    • byteLane
    • CollapseReqResIntoTransaction
    • dataType
    • defnMasterSlave
    • defnPVandPVT
    • defnTransaction
    • DynamicCastExperiment
    • nbTransact
    • passByReference
    • PayloadEvent
    • PolimorphicProtocolUsingMultipleInheritance
    • PolymorphicProtocolUsingMultipleInheritance
    • PolymorphicTransactionUsingMultipleInheritance
    • PortPort
    • ProtocolDefiner
    • PVandPVTlifespans
    • ReturnEvents
    • sameDeltaDifferentThread
    • sharedPTR
    • TimedUntimed
    • TimingEncoding
    • TimingUpdates
    • transport
    • useOCP
    • whyAttributes
  • ExtensionMechanism
  • GILImplementation
  • GreenBusEIS
  • GreenBusGroup
  • GreenBusMilestones
  • GreenBusReview
  • GreenBusSpecification
  • ImplementationIdeas
  • QuarkGuide
  • ReviewIntel
  • ReviewStMicro
  • ScratchPad
  • SingleThreadRouter
  • ToDos

Port to Port binding

So called "Port to Port" binding is more "port to export" or "export to export" in reality.

The reason for choosing it at the "interoperability" level is that it is always possible to add a channel (and bind to the channel) at the "user convenience" layer, but the reverse is not true.

Therefore the interoperability layer should NOT assume a channel, and should operate over port to export binding.

‹ PolymorphicTransactionUsingMultipleInheritanceupProtocolDefiner ›
  • Printer-friendly version

Posted January 8th, 2008 by MarkBurton

 
Copyright GreenSocs Ltd 2005. GreenSocs®; is the trading name of GreenSocs Ltd. Registered in England and Wales with registered number 05379256. Registered office 10 Wellington Street, Cambridge CB1 1HW.