C2MS 1.2b1 RTF Avatar
  1. OMG Issue

C2MS12 — Add a Message Exchange Pattern (MEP) for a component to forward requests/responses

  • Key: C2MS12-11
  • Status: closed  
  • Source: NASA ( Mr. John Bugenhagen)
  • Summary:

    Some services may depend on other services to satisfy a request. Create a MEP that discusses and shows how this could work.

  • Reported: C2MS 1.0 — Tue, 23 Jun 2020 16:52 GMT
  • Disposition: Closed; No Change — C2MS 1.2b1
  • Disposition Summary:

    Close as unnecessary

    Short of sending a new request message with a new Destination Component, any forward of a message would have to take place outside the middleware flow of messages. In the former case, this follows the already-exisitng request/response MEP. With the latter, there is no MEP necessary as functional delegation is a normal software concept that would be handled invisibly to C2MS messages.

    Additionally, in light of other MEP changes needed to fix broken MEPs, this seems very minor and superfluous.

    Therefore, closing this as no-change.

  • Updated: Mon, 30 Mar 2026 14:00 GMT