Changes between Version 1 and Version 2 of HackageDB/2.0/Architecture/Types
- Timestamp:
- 10/02/10 08:27:48 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HackageDB/2.0/Architecture/Types
v1 v2 16 16 17 17 The [Resource] field is the most important one: it defines which pages the 18 feature will serve. The backup fields, which are both optional, can be used 18 feature will serve. If you make a Resource at "/animal/:type/:name", then 19 visiting http://website.com/animal/monkey/alexander will ask that Resource 20 what the best response is. 21 22 The two backup fields, which are both optional, can be used 19 23 to export and import a human-readable representation of a feature's data. This 20 24 is not used for persistent state (since happstack-state is), only for periodic 21 25 snapshots. 22 26 23 Features will probably to provide additional information beside'sthan what's available in the27 Features will probably want to provide additional information other than what's available in the 24 28 `HackageModule` field. For that reason, the actual feature object can be any 25 29 data structure whatsoever, so long as you can get a `HackageModule` from it. … … 32 36 }}} 33 37 34 (The initHooks are a list of miscellaneous actions to do on start up. This could35 berunning hooks, initializing caches, forking maintenance threads, and so on.38 (The initHooks are a list of miscellaneous actions to do on start up. This includes 39 running hooks, initializing caches, forking maintenance threads, and so on. 36 40 The default implementation of this is (const []).) 37 41
