Changes between Version 1 and Version 2 of HackageDB/2.0/Architecture/Types

Show
Ignore:
Timestamp:
10/02/10 08:27:48 (3 years ago)
Author:
mgruen
Comment:

a bit more explanation in intro

Legend:

Unmodified
Added
Removed
Modified
  • HackageDB/2.0/Architecture/Types

    v1 v2  
    1616 
    1717The [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 
     18feature will serve. If you make a Resource at "/animal/:type/:name", then 
     19visiting http://website.com/animal/monkey/alexander will ask that Resource 
     20what the best response is. 
     21 
     22The two backup fields, which are both optional, can be used 
    1923to export and import a human-readable representation of a feature's data. This 
    2024is not used for persistent state (since happstack-state is), only for periodic 
    2125snapshots. 
    2226 
    23 Features will probably to provide additional information beside's than what's available in the 
     27Features will probably want to provide additional information other than what's available in the 
    2428`HackageModule` field. For that reason, the actual feature object can be any 
    2529data structure whatsoever, so long as you can get a `HackageModule` from it. 
     
    3236}}} 
    3337 
    34 (The initHooks are a list of miscellaneous actions to do on start up. This could 
    35 be running 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 
     39running hooks, initializing caches, forking maintenance threads, and so on. 
    3640The default implementation of this is (const []).) 
    3741