1
I Use This!
Inactive

Commits : Listings

Analyzed about 22 hours ago. based on code collected 2 days ago.
May 20, 2023 — May 20, 2024
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Implement test client, and first scenario test 'evil C'
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
Branch-Orchestration implemented in first draft version More... almost 11 years ago
Branch-Orchestration implemented in first draft version More... almost 11 years ago
TestClient, Client encasulation, Evil C test scenario
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
TestClient, Client encasulation, Evil C test scenario
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
TestClient, Client encasulation, Evil C test scenario
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
TestClient, Client encasulation, Evil C test scenario
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
sync down: implemented next steps, including findWinningFirstConflictingDatabaseVersionHeaders and findWinnersWinnersLastDatabaseVersionHeader -- with corresponding tests
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
sync down: implemented next steps, including findWinningFirstConflictingDatabaseVersionHeaders and findWinnersWinnersLastDatabaseVersionHeader -- with corresponding tests
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
3 working test scenarios for update detection in DatabaseVersionUpdateDetector: now able to compare machine histories, detect conflicts and determine a winner. Must test with more scenarios next.
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
3 working test scenarios for update detection in DatabaseVersionUpdateDetector: now able to compare machine histories, detect conflicts and determine a winner. Must test with more scenarios next.
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
Updated database version update detector tests. Creating test scenarios is now a lot easier. Implemented paring mechanism for header serialization.
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
Updated database version update detector tests. Creating test scenarios is now a lot easier. Implemented paring mechanism for header serialization.
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
findLastCommonDatabaseVersionHeader refactored. Adjusted for HeaderParts per client. (No full history in remote Clients, only in Local DB) More... almost 11 years ago
findLastCommonDatabaseVersionHeader refactored. Adjusted for HeaderParts per client. (No full history in remote Clients, only in Local DB) More... almost 11 years ago
commit test class, not working
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
commit test class, not working
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
- Up-Operation-Test detailed More... almost 11 years ago
- Up-Operation-Test detailed More... almost 11 years ago
- Up-Operation test completed with one DatabaseVersion More... almost 11 years ago
- Up-Operation test completed with one DatabaseVersion More... almost 11 years ago
- DatabaseFile introduced with differentation between local und remote (subclasses) - Local.db filecheck fixed More... almost 11 years ago
- DatabaseFile introduced with differentation between local und remote (subclasses) - Local.db filecheck fixed More... almost 11 years ago
Continuing the sync down algorithm description (B) and starting a first implementation prototype in DatabaseVersionUpdateDetector.java: Determines the last common database version for all the clients, then the first conflicting database version, then determines a winner from them. This works fine when the client has full information (all complete branches, see testUpdateDetectorScenario1), but not yet for partial information (see testUpdateDetectorScenario2). Needs to be talked over
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
Continuing the sync down algorithm description (B) and starting a first implementation prototype in DatabaseVersionUpdateDetector.java: Determines the last common database version for all the clients, then the first conflicting database version, then determines a winner from them. This works fine when the client has full information (all complete branches, see testUpdateDetectorScenario1), but not yet for partial information (see testUpdateDetectorScenario2). Needs to be talked over
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
Thoughts about the sync down operation. A scenario that might just work. Although the algorithm descibed is not written down yet.
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
Thoughts about the sync down operation. A scenario that might just work. Although the algorithm descibed is not written down yet.
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
Thoughts about the sync down operation. A scenario that might just work. Although the algorithm descibed is not written down yet.
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
Thoughts about the sync down operation. A scenario that might just work. Although the algorithm descibed is not written down yet.
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago
sync down continuing, sort vector clocks, determine all conflicts, determine the first conflict-free database version headers
Philipp C. Heckel
as Philipp Heckel
More... almost 11 years ago