Improve name for setProxied. Better updateEndToEnd because have any other 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 7e007ca..7532771 100644 (file)
--- a/include/anna/diameter.comm/Message.hpp
+++ b/include/anna/diameter.comm/Message.hpp
@@ -108,11 +108,20 @@ public:
 
   bool fixRequestSequence(HopByHop hbh, EndToEnd ete) throw();
 
-  /** Diameter agents CANNOT modify the end-to-end. True value stands for intermediate agents, false for request originators */
-  bool isProxied() const throw() { return a_proxied; }
+  /**
+   * 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
+   * during 4 minutes even upon reboots). False is used for new request created from end points (originators)
+   * as diameter clients.
+   */
+  bool updateEndToEnd() const throw() { return a_updateEndToEnd; }
 
-  /** Diameter agents CANNOT modify the end-to-end. True value stands for intermediate agents, false for request originators */
-  void setProxied(bool proxied = true) throw() { a_proxied = proxied; }
+  /**
+   * In general, diameter agents CANNOT modify the end-to-end value during sending the message to the peer.
+   * The appropiate behaviour must be configured before sending the message. By default, the diameter::comm
+   * message will sequence the end-to-end increasing the initial value created during session establishment.
+   */
+  void updateEndToEnd(bool update) throw() { a_updateEndToEnd = update; }
 
 
   // Statistics
@@ -140,7 +149,7 @@ public:
     a_requestClientSessionKey = ""; // means unknown/unset
     a_requestHopByHop = 0;
     a_requestEndToEnd = 0;
-    a_proxied = false;
+    a_updateEndToEnd = true;
   }
 
 
@@ -164,7 +173,7 @@ private:
   std::string a_requestClientSessionKey;    // idem for request which was received from servers
   HopByHop a_requestHopByHop; // application backup for hop-by-hop in order to restore on answer receive
   EndToEnd a_requestEndToEnd; // application backup for end-to-end in order to restore on answer receive
-  bool a_proxied; // end-to-end will be kept
+  bool a_updateEndToEnd; // end-to-end will be updated
 
   void send(ClientSession&) const throw(anna::RuntimeException);
   void send(ServerSession&) const throw(anna::RuntimeException);