Revision: 14268 Author: adrian.chadd Date: Sun Aug 9 23:01:49 2009 Log: Edited wiki page through web user interface. http://code.google.com/p/lusca-cache/source/detail?r=14268
Modified: /wiki/LuscaArchitectureRangeRequests.wiki ======================================= --- /wiki/LuscaArchitectureRangeRequests.wiki Sun Aug 9 22:47:36 2009 +++ /wiki/LuscaArchitectureRangeRequests.wiki Sun Aug 9 23:01:49 2009 @@ -30,6 +30,12 @@ = Issues and Limitations = +== Aborting transfers on cachable range request replies == + +TODO: flesh this out and think about how a "slightly better" hack would look + +== Inability to cache actual range replies! == + == 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? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
