| ... | @@ -4,7 +4,19 @@ This document governs best practices for writing CFML for inLeague applications | 
... | @@ -4,7 +4,19 @@ This document governs best practices for writing CFML for inLeague applications | 
| 
 | 
 | 
 | 
 | 
| 
 | 
# Table of Contents
 | 
 | 
# Table of Contents
 | 
| 
 | 
 | 
 | 
 | 
| 
 | 
1. [Writing API Endpoints](#writing-api-endpoints)
 | 
 | 
1. [Function Architecture: Handlers, Services, Models](#function-architecture)
 | 
 | 
 | 
 | 
2. [Writing API Endpoints](#writing-api-endpoints)
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
## Function Architecture
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Handlers' job is to handle input. Their job is not to apply business rules, or even be aware of business rules. They are concerned with:
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
* processing incoming data in the request scope
 | 
 | 
 | 
 | 
* either validating the request or else referring the request collection to a validation layer 
 | 
 | 
 | 
 | 
* referring the validated request to the business object responsible for Doing The Thing
 | 
 | 
 | 
 | 
* returning or rendering a result to satisfy the request
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
(TODO)
 | 
| 
 | 
 | 
 | 
 | 
| 
 | 
## Writing API Endpoints
 | 
 | 
## Writing API Endpoints
 | 
| 
 | 
 | 
 | 
 | 
| ... |  | 
... |  | 
| ... |  | ... |  |