Changes between Version 3 and Version 4 of HackageDB/2.0/Architecture

Timestamp:

08/06/10 01:01:58 (3 years ago)

Author:

mgruen

Comment:

more about fragility of syncing

HackageDB/2.0/Architecture

@@ -182 +182 @@
  * User groups have a messy interface. Although each feature should define and manage their own, it is still desirable to map a user to the groups they are in. Presently this is done by mapping a !UserId to a bunch of URIs, and each URI to a group description.
  * Too many cross-cutting Happstack queries. Features should hide Happstack queries and updates in their own wrappers, which may also call hooks and do any related maintenance.
- * The system of relying on hooks and filters to keep features in sync is fragile, and it's easy to miss something and get inconsistent results. Perhaps there should be a package mapping which has the express purpose of syncing with the main index.
+ * The system of relying on hooks and filters to keep features in sync is fragile, and it's easy to miss something and get inconsistent results. Perhaps there should be a package mapping which has the express purpose of syncing with the main index. This is one of the disadvantages of using native Haskell types, though the advantages are plenty.
  * As ever, eliminate as much boilerplate as sanely possible.