emergency-if — archive

[Donald McGarry]

Lee/Gary/Others: My apologies....That did not come out as it was represented in my head as intended in the email. My point was not to say that folks were not using it at all, nor to say that it was only for point to point non-redistribution. I was speaking more of the "advanced" routing component that Dave is speaking of. Bottom line is I want this thing to flourish and grow its adoption base beyond where we are now. I don't think our concern or focus can be on specific large-scale systems with requirements without technical details to support their needed requirements. My use case is this: 1. Field paramedic sends a message to an exposure system with his sender role and keywords describing message content, which includes multiple payloads. Field paramedic doesn't know the state of the command structure for multiple reasons: bandwidth of always pushing around the state of command; changing people in roles; explicit addressing locks down adding unintended producers / consumers of data, which is bad in some cases. 2. Message system routes and exposes data based on current state of ICS / command model. This is based on predefined valuelists for terminology, roles, and keywords that can hosted at destination URI's, but can also be pushed to endpoint nodes; the