Dashboard > CI Development > ... > Messaging Service > MS Iteration4
Log In   View a printable version of the current page.
CI Development
MS Iteration4
Added by Michael Meisinger , last edited by Michael Meisinger on Jul 16, 2009  (view change)
Labels: 
(None)

Scope

Develop and describe a prototype for the OOI messaging service, comprising messaging service mechanisms based on a solid theory for network IPC, and application clients to interface with the messaging service.

Tasks

  • Develop a client for the messaging service (Magnet)
    • Applications are represented by role protocols, which rely on connections to their role protocol counterparts via names. Together this realizes an application protocol (interaction pattern) that exists within a contractual context
    • Application role protocols are implemented as Twisted protocols for this iteration
    • Magnet via Twisted provides a connect, as well as a request listener with reply facility using the messaging service
    • Magnet provides name to address lookup
    • Magnet separates connection and protocol configurator from the definition of the role protocols
    • Magnet provides several telling examples
  • Messaging service specification
  • DIF-AMQP Integration
  • Develop an end-to-end story for reporting and reviewing

Design

The figure below shows the design of a service application using the Magnet messaging client. Magnet works in conjunction with the Twisted framework and txAMQP.


The figure below shows a scenario of resource agents interacting using Magnet messaging service clients



 

Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators