Revision: 14438 Author: adrian.chadd Date: Sun Feb 28 06:19:39 2010 Log: Document what's going on a little.
http://code.google.com/p/lusca-cache/source/detail?r=14438 Modified: /branches/LUSCA_HEAD/src/client_side_purge.c ======================================= --- /branches/LUSCA_HEAD/src/client_side_purge.c Sun Feb 28 05:49:39 2010 +++ /branches/LUSCA_HEAD/src/client_side_purge.c Sun Feb 28 06:19:39 2010 @@ -5,6 +5,22 @@ #include "client_side_purge.h" +/* + * The client-side purge path is a bit convoluted. + * + * The initial PURGE request will cause a call to clientPurgeRequest() via + * clientProcessRequest(). clientProcessRequest() will then schedule + * a lookup to swap the object in via clientCacheHit(). + * + * clientCacheHit() will then parse the headers and then eventually kick + * the request either back here directly or in the case of a swap in + * failure, indirectly via clientProcessMiss(). + * + * Once the headers have been swapped in the purge request completes + * normally. The GET/HEAD method objects are individually poked + * to be removed; there's some Vary magic going on and then a response + * is returned to indicate whether the object was PURGEd or not. + */ void clientPurgeRequest(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.
