Commits

Jakub Oboza  committed 6c8ef2e

link to debugging gives 404 i think it should be changed to WebmachineDebugging

  • Participants
  • Parent commits 777fa23

Comments (0)

Files changed (1)

File WebmachineResources.wiki

 -include_lib("webmachine/include/webmachine.hrl").
 }}}
 
-All webmachine resources should define and export {{{init/1}}}, which will receive a configuration property list from the [[DispatchConfiguration|dispatcher]] as its argument. This function should, if successful, return {{{ {ok, Context} }}}. Context is any term, and will be threaded through all of the other webmachine resource functions.  Alternately, the resource can go into debugging mode by returning {{{ {{trace, Dir}, Context} }}} instead -- see [[DebuggingResources]] for more information on tracing.
+All webmachine resources should define and export {{{init/1}}}, which will receive a configuration property list from the [[DispatchConfiguration|dispatcher]] as its argument. This function should, if successful, return {{{ {ok, Context} }}}. Context is any term, and will be threaded through all of the other webmachine resource functions.  Alternately, the resource can go into debugging mode by returning {{{ {{trace, Dir}, Context} }}} instead -- see [[WebmachineDebugging]] for more information on tracing.
 
 All webmachine resource functions are of the signature:
 
 | POST-processing function named as a Handler by content_types_accepted |  | X | {{{ true }}} |  |
 
 The above are all of the supported predefined resource functions. In addition to whichever of these a resource wishes to use, it also must export all of the functions named in the return values of the content_types_provided and content_types_accepted functions with behavior as described in the bottom two rows of the table.
-