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

Timestamp:

08/06/10 01:03:35 (3 years ago)

Author:

mgruen

Comment:

misc formatting

HackageDB/2.0/Architecture

@@ -126 +126 @@
 At the very top, the Resource object is created, then GET/PUT methods are added
 using record update notation. Both resourceGet and resourcePut expect a
-[(!Content, !DynamicPath -> !ServerPart Response)] object, where the first argument
+[(Content, !DynamicPath -> !ServerPart Response)] object, where the first argument
 is a content-type in case multiple formats are wanted. (See formats.) They
 each return a text/plain response, so "txt" is used.
@@ -141 +141 @@
  * Hooks. Hooks are generally called after an update happens, and they can take any number of arguments and run an IO action. They may call other Hooks in turn, but they shouldn't take too long. They are processed in sequence, and run in the reverse order of their adding.
  * Filters are generally called before an update happens, with the ability to stop the event, or inject some value into it. They can also take any number of arguments, and return a typed IO result. They use the same internal representation as Hooks, but have more specific utility functions.
- * Basic and digest authentication. This authenticates an access control list against the user database using a stateless approach.
- * Backup. One of the more complicated backup types is RestoreBackup, which each feature wanting to import data should implement. (explain)
+ * Basic and digest authentication. This authenticates an access control list against the user database using stateless HTTP.
+ * Backup. One of the more complicated backup types is !RestoreBackup, which each feature wanting to import data should implement. (explain)
 
 == Core Hackage types ==