/**
* 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; }
/**