Project

General

Profile

Bug #11734

persistence caches for remote databases

Added by Constantin Asofiei about 8 hours ago. Updated about 8 hours ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Constantin Asofiei about 8 hours ago

FWD allows server A to connect to remote FWD server B, to access the database instance managed by server B. This requires directory configuration for the remote FWD server access, and also a direct JDBC connection for the database.

Server A AFAIK at this time uses only remote dirty share, persistence and primary key calculations. Other caches (like FFCache, ORM Session cache) for the database served by server B, I think live on server A, while they can never be invalidated by server B.

This task is meant to investigate and find solutions for these cases.

Also available in: Atom PDF