backup/EWF
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated Writing the handlers (markdown)

Browse Source
This commit is contained in:
colin-adams
2013-08-13 08:24:05 -07:00
parent 9c8bc59224
commit 123fc8252e
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Writing-the-handlers.md
View File

@@ -18,6 +18,8 @@ The first one makes the request entity from a PULL or POST request available to
The next four make the results of content negotiation available to your routines. The last one makes an HTTP_HEADER available to your routines. You should use this rather than create your own, as it may contain a **Vary** header as a by-product of content negotiation. The next four make the results of content negotiation available to your routines. The last one makes an HTTP_HEADER available to your routines. You should use this rather than create your own, as it may contain a **Vary** header as a by-product of content negotiation.
All six names are defined as constants in WSF_SKELETON_HANDLER, to make it easier for you to refer to them.
## Implementing the routines declared directly in WSF_SKELETON_HANDLER ## Implementing the routines declared directly in WSF_SKELETON_HANDLER
### check_resource_exists ### check_resource_exists