| 2009-08-19 12:47:13 |
Paul Everitt |
description |
As Shane discovered working on the bug where profiles could be seen by the wrong people, he found that we weren't using workflow transitions in the GSA sync.
As part of this ticket, try to address that point. Along the way, improve the test coverage for the sync logic.
Furthermore, based on the conversation with Ajo, see if we can start steering sync in a more generic direction. Specifically, make it easier for other systems to implement. Ideally, we would make all state about sync reside in the client, similar to a web caching architecture where servers don't have to record state about clients. With a model like this, the "master" provides a read-only view of data. (Ajo, Shane, and I chatted about this direction.) |
As Shane discovered working on the bug where profiles could be seen by the wrong people, he found that we weren't using workflow transitions in the GSA sync.
As part of this ticket, try to address that point.
Other Part, not done
======================
Along the way, improve the test coverage for the sync logic.
Furthermore, based on the conversation with Ajo, see if we can start steering sync in a more generic direction. Specifically, make it easier for other systems to implement. Ideally, we would make all state about sync reside in the client, similar to a web caching architecture where servers don't have to record state about clients. With a model like this, the "master" provides a read-only view of data. (Ajo, Shane, and I chatted about this direction.) |
|
