|
From: Peter W. <pw-...@te...> - 2004-03-10 02:05:41
|
Hi, I'm currently in the situation of needing to find an elegant way of having multiple processes all use caching turned on and yet have them track changes made in one of the other processes. eg. Process A is running doing mainly reads, while process B is occasionally making changes, process A in this situation would ideally be able to deal with this and see the changed objects. Currently I'm doing this by assuming and accepting that process B will occasionally be out of sync with he reality of the database by having it having it kill itself periodically. Now this works but is far from elegant and ends up defeating the use of a cache which is extremely handy in a process that is really only deals with the database read-only. How have others dealt with this? Is something like putting the cache in shared memory feasible? -- peter w. |
