-// ANNA - Anna is Not Nothingness Anymore
-//
-// (c) Copyright 2005-2014 Eduardo Ramos Testillano & Francisco Ruiz Rayo
-//
-// http://redmine.teslayout.com/projects/anna-suite
-//
-// Redistribution and use in source and binary forms, with or without
-// modification, are permitted provided that the following conditions
-// are met:
-//
-// * Redistributions of source code must retain the above copyright
-// notice, this list of conditions and the following disclaimer.
-// * Redistributions in binary form must reproduce the above
-// copyright notice, this list of conditions and the following disclaimer
-// in the documentation and/or other materials provided with the
-// distribution.
-// * Neither the name of the copyright holder nor the names of its
-// contributors may be used to endorse or promote products derived from
-// this software without specific prior written permission.
-//
-// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-//
-// Authors: eduardo.ramos.testillano@gmail.com
-// cisco.tierra@gmail.com
+// ANNA - Anna is Not Nothingness Anymore //
+// //
+// (c) Copyright 2005-2015 Eduardo Ramos Testillano & Francisco Ruiz Rayo //
+// //
+// See project site at http://redmine.teslayout.com/projects/anna-suite //
+// See accompanying file LICENSE or copy at http://www.teslayout.com/projects/public/anna.LICENSE //
#ifndef anna_diameter_codec_EngineImpl_hpp
* Defines behaviour mode regarding when to validate a message: before encoding, after decoding (by default), always or never
* Anyway validation procedure may be called at any moment (#valid)
*/
- struct ValidationMode { enum _v { BeforeCoding, AfterDecoding /* default */, Always, Never /* optimization */ }; };
+ struct ValidationMode { enum _v { BeforeEncoding, AfterDecoding /* default */, Always, Never /* optimization */ }; };
/**
* Defines behaviour mode regarding when to fix a message: before encoding (by default), after decoding, always or never.
* hide any validation problem regarding Avps position at any level.
* Anyway fix procedure may be called at any moment (#fix)
*/
- struct FixMode { enum _v { BeforeCoding /* default */, AfterDecoding, Always, Never /* optimization */ }; };
+ struct FixMode { enum _v { BeforeEncoding /* default */, AfterDecoding, Always, Never /* optimization */ }; };
// Creators
/**
* By default, the user will select the appropiate stack id depending on the context (see #setDictionary), but
* some applications could consider interesting automatic stack selection based on managed messages (incoming
- * decoded ones, or built messages to be encoded). By default, no changes are done through the engine. Multithreaded
- * processes should have a unique codec engine for each managed stack (this selection is disabled by default, then
- * you don't have to worry about), but mono processes with multistack implementation over the same-unique engine,
- * should activate this to have the commonly recommended way to choose the stack: using the Application-Id value.
+ * decoded ones, or built messages to be encoded). By default, on engine construction, no changes are done.
+ * Multithreaded processes should have a unique codec engine for each managed stack (then you don't have to
+ * worry about), but mono processes with multistack implementation over the same-unique engine, should activate
+ * this to have the commonly recommended way to choose the stack: using the Application-Id value.
*
* @warning do not activate in case of multithreaded applications.
* @param enable Activates/deactivates the stack selection from the Application-Id value within the message header.
@return True if selection is done with the Application-Id. False if no selection is performed (user responsibility).
*/
- bool selectStackWithApplicationId (void) throw() { return a_selectStackWithApplicationId; }
+ bool hasSelectStackWithApplicationId (void) throw() { return a_selectStackWithApplicationId; }
/**