Revision: 14403 Author: adrian.chadd Date: Sat Feb 13 22:52:19 2010 Log: Document what clientProcessRequest() does.
http://code.google.com/p/lusca-cache/source/detail?r=14403 Modified: /branches/LUSCA_HEAD/src/client_side.c ======================================= --- /branches/LUSCA_HEAD/src/client_side.c Thu Feb 11 23:26:11 2010 +++ /branches/LUSCA_HEAD/src/client_side.c Sat Feb 13 22:52:19 2010 @@ -2594,6 +2594,31 @@ return LOG_TCP_HIT; } +/*! + * @function + * clientProcessRequest + * @abstract + * Begin processing a fully validated request + * @description + * This function begins the processing chain of a request and determines + * whether to begin forwarding upstream or whether the object already + * exists in some form. + * + * It handles CONNECT, PURGE and TRACE itself. The rest of the methods + * are punted to the forwarding/store layer for handling. + * + * If there's no StoreEntry associated with the object, the request is + * punted to clientProcessMiss() for further handling. + * + * If there's a StoreEntry, then some previous processing has performed + * the client lookup and successfully found an object to attach to. + * In this case, a store client is created and registered and the first + * copy of the object reply is queued, which will eventually result in + * the request being made if required, and the reply being fed from + * the store via either the forwarding or the cache layer. + * + * @param http clientHttpRequest to begin processing + */ void clientProcessRequest(clientHttpRequest * http) { -- You received this message because you are subscribed to the Google Groups "lusca-commit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/lusca-commit?hl=en.
