This document was generated from CDN thread
Created by: null on 03-12-2004 02:30:49 AM
I have an application that's broken into four separate sections (applications) which all of them need to share the same session data.
Essentially a router application handles the incoming call, then routes the caller to the appropriate application to handle the caller's request. The caller then can be routed to another application based on conditions. I'm having problems accessing the session data for the initial application (router application) when there are more than two application transfers performed. Also, how much data can be stored at the session level? Any suggestions?
Subject: RE: Session Data and Application Transfers
Replied by: Michael Bochynski on 06-12-2004 06:05:26 PM
Hi,
Audium adds as a prefix the application's name to any session data being transferred to the new application, so the new name would be APPNAME_VARIABLENAME.
For example, if you have session data named VARIABLE1, and transfer it from application A to application B, in the application B your transferred session data will be available as A_VARIABLE1.
Note that the prefix will be added to the existing variable name every time you do a transfer, hence during the next transfer from application B to the application C, the data would be renamed to B_A_VARIABLE1.
Audium does not limit the amount of session data that can be created, however the size of data can be limited by Tomcat configuration and/or memory limitations on the machine.
Hope this helps,
Michael