Thread: Dynamically overriding Session attributes

A SessionType would define reasonable static default values, but we now have the flexibility to override some of the attributes dynamically and programmatically.
These dynamic overrides were first introduced in 4.0 because it was a pain for users to be boxed into static configuration. For example, notice that session priority is also tied to a SessionType. In past, users would have to define a SessionType for each priority they needed to use. It was a pain to define and maintain all of these SessionTypes in the application profile, especially if the SessionTypes were identical in every aspect other than their priorities.
The same theory applies to the case when you want to dynamically override default service among different multiple services tied to the session.

Here are the API calls to programmatically override the attributes.

Code:

void setServiceName (const char * serviceName) throw SoamException<classSoamException.html>)
void setSessionPriority  (const SoamInt32  priority)  throw (SoamException)

For more detail, please refer to the API document at the Knowledge Center

Are Name and Priority the only 2 that can be dynamically set? ... what about other session attributes such as Tag, Flag, etc ...

You're right. There are other SessionCreationAttributes such as, name, flags, common data, callback, tag and service name that can be *programmatically* set in your client code. However, according to the schema of Symphony application profile (%SymphonyDE_HOME%/4.0/schema/ApplicationProfile.xsd), only session name, priority and service name can be statically set in the application profile.