+ 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 nodes will sequence the End-To-End value when sending new requests.
+ * A 'false' value stands for intermediate agents (must keep end-to-end during 4 minutes even upon reboots).
+ */
+ bool endToEndSequenced() const throw() { return a_endToEndSequenced; }
+
+ /**
+ * By default, the diameter::comm message will sequence the end-to-end increasing the initial value created
+ * during session establishment. Anyway you could change this behaviour with this method.
+ *
+ * @see sequenceEndToEnd
+ */
+ void forwardEndToEnd() throw() { a_endToEndSequenced = false; }
+
+ /**
+ * By default, the diameter::comm message will sequence the end-to-end increasing the initial value created
+ * during session establishment. Anyway you could set again this behaviour with this method.
+ *
+ * @see forwardEndToEnd
+ */
+ void sequenceEndToEnd() throw() { a_endToEndSequenced = true; }