New ApplicationMessageOamModule in diameter::comm, to dynamically manage application...

[anna.git] / include / anna / diameter.comm / Message.hpp

diff --git a/include/anna/diameter.comm/Message.hpp b/include/anna/diameter.comm/Message.hpp
index 7532771..b5cb459 100644 (file)
--- a/include/anna/diameter.comm/Message.hpp
+++ b/include/anna/diameter.comm/Message.hpp
@@ -105,9 +105,12 @@ public:
   void setRequestEndToEnd(EndToEnd ete) throw() { a_requestEndToEnd = ete; }
   CommandId getCommandId(bool &isRequest) const throw();
   CommandId getCommandId() const throw() { bool dummy; return getCommandId(dummy); }
+  ApplicationId getApplicationId() const throw();
 
   bool fixRequestSequence(HopByHop hbh, EndToEnd ete) throw();
 
+  // http://diameter-protocol.blogspot.com.es/2011/05/diameter-message-structure-and-message.html
+
   /**
    * In general, diameter agents CANNOT modify the end-to-end value during sending the message to the peer.
    * That 'true' value stands for intermediate agents and also for retransmissions (must keep end-to-end