Revision: 14264
Author: adrian.chadd
Date: Sun Aug  9 11:50:12 2009
Log: Created wiki page through web user interface.
http://code.google.com/p/lusca-cache/source/detail?r=14264

Added:
  /wiki/LuscaArchitectureRangeRequests.wiki

=======================================
--- /dev/null
+++ /wiki/LuscaArchitectureRangeRequests.wiki   Sun Aug  9 11:50:12 2009
@@ -0,0 +1,33 @@
+#summary How Range Requests are handled inside Lusca
+
+= Introduction =
+
+The Lusca range request support handles range request replies to cache  
content. It does not currently handle caching range replies from  
upstreams/origins; it also has some issues with complicated and overlapping  
range requests.
+
+= Overview =
+
+There are multiple parts to the range request support.
+
+The client-side code (src/client_side.c) parses the headers, sets the  
range request field in the request_t object with the range lists and then  
forwards the request normally.
+
+The decision whether to issue a range request or a full object request is  
done in the server-side code (src/http.c).
+
+The client-side code then parses the headers from the store and determines  
whether the reply should be returned as-is (ie, the reply is a partial  
reply itself) or whether the reply is a full object reply and the request  
ranges should be fetched in-order, skipping regions which are not requested.
+
+= Details ==
+
+== Parsing Range Requests ==
+
+== Determining whether to forward a Range request ==
+
+== Handling range replies from the store ==
+
+= Issues and Limitations =
+
+== Non-range replies to range requests ==
+
+TODO: I'm not certain what will happen if an upstream/origin returns a  
partial reply that contains more than the requested ranges. I -believe- it  
will just be returned verbatim. This hasn't yet been an issue in the wild?
+
+== Overlapping range requests ==
+
+TODO: find the reference to the Squid issue with overlapping/complicated  
ranges!

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to