Here's some legwork...you can drill-down to section 14.25 of the page below where it describes the If-Modified-Since header. Basically, any Get with this header including a timestamp can be compared to the timestamp for the matching Entity to determine whether to respond normally (return the image) or respond with a 304 (Not modified) response. I think the trick is determining the compare granualarity since the server time and the client time are never exactly in sync. Perhaps the granularity for comparison should be down to the minute, not seconds and definitely not millisecond. What do you think?
http://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html On Oct 23, 10:08 am, Vince Bonfanti <vbonfa...@gmail.com> wrote: > No, not yet. It's on the TODO list (see line 171 of the GaeVfsServlet > source code). If you--or anyone else--wants to add this I'll be happy > to accept a patch. > > Vince > > > > On Fri, Oct 23, 2009 at 11:42 AM, Diana Cruise <diana.l.cru...@gmail.com> > wrote: > > > In terms of performance does gaevfs accmmodate http resource timestamp > > checks to avoid re-downloading repeated requests for the same images?- Hide > > quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
