Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: None
    • Labels:
      None
    • Proposal:
      Hide

      Add an element called: <route>
      Every server that handles the CAP message along the way will append its "stamp" to the route.
      Of course, this could break a signature, so it may not be a good idea if the message is signed by the originator, unless the originator is able to exclude the <route> element from the signature.

      Show
      Add an element called: <route> Every server that handles the CAP message along the way will append its "stamp" to the route. Of course, this could break a signature, so it may not be a good idea if the message is signed by the originator, unless the originator is able to exclude the <route> element from the signature.
    • Resolution:
      Hide

      need to close this one. due to signature requirements, must have an envelope use EDXL-DE distribution element for routing.

      Show
      need to close this one. due to signature requirements, must have an envelope use EDXL-DE distribution element for routing.

      Description

      Many times when troubleshooting or auditing, it is useful to know the "route" or "path" that the CAP message took to arrive to its destination. The assumption here is that the system is using its own custom transport protocol, and the wrapper of the CAP message is unknown. In a complex network it may be useful to know the path for optimizations and load balancing

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tpetel Tomer Petel (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: