Asynchronous Method Invocation for               CORBA Component Model                     (AMI4CCM)                    Re...
Document numbers       mars/12-01-01 (Asynchronous Method Invocation for CORBA       Component Model (AMI4CCM) revised sub...
The RFP asks for        Extend CCM with a standardized way of doing        asynchronous method invocation using the connec...
Global overview        Asynchronous invocations for CCM          –   Does not require CORBA AMI support but is modeled    ...
Relationship to CCM        AMI4CCM is an extension to CORBA        Component Model        Is in itself not a attempt to mi...
Pragmas        Standardize pragmas make it possible to        enable AMI4CCM at a fine grained level          –   #pragma ...
Implied IDL conversion        Conversion of user IDL to a set of implied IDL        interfaces: AMI4CCM sendc interface an...
AMI4CCM Connector       Connectors are defined in IDL       AMI4CCM implementation can generate a       concrete AMI4CCM c...
Deployment viewCopyright © 2012                     Page 9
Example implementation         Example implementation available as part of         CIAO (x.0.7 and newer support the revis...
Next steps        V2V        AB        FTFCopyright © 2012                Page 11
Upcoming SlideShare
Loading in …5
×

AMI4CCM revised submission presentation

558 views

Published on

This is the presentation which Remedy IT gave to the OMG MARS working group regarding its revised submission for AMI4CCM

Published in: Technology, Sports
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
558
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

AMI4CCM revised submission presentation

  1. 1. Asynchronous Method Invocation for CORBA Component Model (AMI4CCM) Revised Submission mars/2012-03-30Copyright © 2012 Page 1
  2. 2. Document numbers mars/12-01-01 (Asynchronous Method Invocation for CORBA Component Model (AMI4CCM) revised submission) mars/12-02-20 (AMI4CCM revised submission - Machine- readable IDL) mars/12-02-21 (AMI4CCM revised submission - inventory file) mars/12-03-01 (Asynchronous Method Invocation for CORBA Component Model (AMI4CCM) revised submission) mars/12-03-02 (AMI4CCM revised submission errata)Copyright © 2012 Page 2
  3. 3. The RFP asks for Extend CCM with a standardized way of doing asynchronous method invocation using the connector concept. Provide a callback model where the user component is called back with the received reply or exception in case of a failure. Allow to be used with simplex and multiplex receptacles Allow multiple invocations to be outstanding to the same server component Explain how AMI4CCM will be deployed and configured.Copyright © 2012 Page 3
  4. 4. Global overview Asynchronous invocations for CCM – Does not require CORBA AMI support but is modeled based on CORBA AMI – Details of asynch invocation hidden from component business logic Set of implied IDL rules – Creates implied connector and interfaces used by component business logic – Requires annotation through pragmas AMI4CCM connectorCopyright © 2012 Page 4
  5. 5. Relationship to CCM AMI4CCM is an extension to CORBA Component Model Is in itself not a attempt to migrate from CORBA Component Model to a Common Component ModelCopyright © 2012 Page 5
  6. 6. Pragmas Standardize pragmas make it possible to enable AMI4CCM at a fine grained level – #pragma ami4ccm interface "<fully qualified interface name>" – #pragma ami4ccm receptacle "<fully qualified receptacle name>"Copyright © 2012 Page 6
  7. 7. Implied IDL conversion Conversion of user IDL to a set of implied IDL interfaces: AMI4CCM sendc interface and reply handler Similar to the CORBA AMI implied rules and naming but only uses local interfaces and no valuetypes See section 7.{3,4,5} for the detailsCopyright © 2012 Page 7
  8. 8. AMI4CCM Connector Connectors are defined in IDL AMI4CCM implementation can generate a concrete AMI4CCM connector module CCM_AMI {   // Base class for all AMI4CCM connectors   connector AMI4CCM_Base {   };   // Templated Connector module for AMI4CCM. Expects   // two template arguments, the original interface and   // its AMI4CCM counterpart   module Connector_T<interface T, interface AMI4CCM_T> {     porttype AMI4CCM_Port_Type {       provides AMI4CCM_T ami4ccm_provides;       provides T ami4ccm_sync_provides;       uses T ami4ccm_uses;     };     connector AMI4CCM_Connector : AMI4CCM_Base {       port AMI4CCM_Port_Type ami4ccm_port;     };   }; }; // Creating a concrete AMI4CCM module CCM_AMI::Connector_T<StockManager, AMI4CCM_StockManager> AMI4CCM_StockManager_Connector;Copyright © 2012 Page 8
  9. 9. Deployment viewCopyright © 2012 Page 9
  10. 10. Example implementation Example implementation available as part of CIAO (x.0.7 and newer support the revised submission) Supported by CoSMIC, Artisan, and Zeligsoft as CCM/D&C modeling toolsCopyright © 2012 Page 10
  11. 11. Next steps V2V AB FTFCopyright © 2012 Page 11

×