A Cross-Context Flow is handled by sending required data between applications participating in Cross-Context Flows using a URLConnection. This data is necessary for transmitting state information and application data such as Views. This data is transmitted using serialization across the connection. The process of serializing and de-serializing the data, along with the communication across the connection, causes performance degradation.
In addition, for Links and Transfers that cause a display from the flowed-to context, the data must be stored to a Java Message Service (JMS). This makes the data available when the browser is redirected to the flowed-to context. This additional storage and retrieval of data will also impact performance.
The larger the view sizes being sent between procedures, the more significant this impact will be. While this may not be a problem when testing a new element destined to be ultimately deployed in the same web application, it should be considered in a system architecture that plans production use of Cross-Context Flows.
|
Copyright © 2013 CA.
All rights reserved.
|
|