R
Ravi Sankar
Guest
I would think the best solution to your problem is to always use Openedge Database for all session requests (Read/Write/Update) With this approach, is there any performance impact that is affecting usability of the application from end user point of view? If the session requests are overwhelming the application requests, does separate database for session data help? PASOE session replication could also be a solution, if both your PASOE instances are in the same network and discoverable. AFAIK, PASOE session replication is in-memory and can't be backed by persistent store. I could be wrong, though.
Continue reading...
Continue reading...