D
dbeavon
Guest
Can you describe the problem a bit more clearly? Do you have two different abl apps (and webapps) that are each connected to a different version of the database? And one of the databases has a bit of additional latency (and is read-only)? Will the front-end continue to be webspeed? Are the "sessions" that you mentioned for tracking the front-end users (ie. they are long-lived sessions), or are they created for the sole purpose of the short-lived work that is being done in PASOE? >>If I wish to offload specifics read-only requests to the OE-Replication database. I don't see why you can't use a connection to *both* the primary *and* replicated versions of the PASOE abl app. One is for managing your session data and the other is for offloading the larger reads (or whatever). Why do the two PASOE need to share any "session" data? The front-end can coordinate with a common ID of some kind and allow each side to "maintain" the portion of the session-state that it cares about. For "maintaining" the PASOE session, you could easily use session-managed APSV model. This will hold the data in PASOE memory between round-trips so the front-end doesn't have to keep reminding the PASOE application about the full session state.
Continue reading...
Continue reading...