Cheng-Dar Yang | Hi Janine
1. This question was asked via another channel lastweek... By adding large amount of data to the session will increase the per session footprint in the JVM. Also as session size increase the number of concurrent session decreases. This also means that JVM garbage collection will occur more often, and therefore, more load on the system and the performance suffers. There is no real way to predict the impact other then to prototype the app and execute performance tests.
2. The rule of thumb for pages vs. apps is to break up the application down to logical units. If an unit can/will be reused by other apps, then it make sense to create multiple apps. However, there is more overhead in passing from app to app. So if a caller is expected to take a limited call path, then you should try to contain it to a single app, unless development of a very large app becomes an issue.
3. Currently for CVP customers, there is no developer forum. Things are in the works, but are a long way from completion. As for code sharing, we will not provide that for CVP customers b/c of support issues.
Regards, Cheng |
| Please sign in to flag this as inappropriate. |