OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (EMERGENCY-38) add a route hint to CAP messages

    [ https://issues.oasis-open.org/browse/EMERGENCY-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59365#comment-59365 ] 

Tomer Petel commented on EMERGENCY-38:

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

> add a route hint to CAP messages
> --------------------------------
>                 Key: EMERGENCY-38
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-38
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>            Reporter: Tomer Petel
> 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

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]