#105 ✓closed
Jonathan Lister

Exploit HTTP headers for performance

Reported by Jonathan Lister | October 7th, 2010 @ 11:35 AM | in 0.9.3

i. If 304 not-modified is sent, don't redraw, just move the blobs and the x-axis over.
ii. If enough time has passed since a redraw that a new x-axis label is required, redraw

Comments and changes to this ticket

  • Jonathan Lister

    Jonathan Lister October 7th, 2010 @ 01:19 PM

    • State changed from “new” to “open”
    • Milestone order changed from “40” to “0”

    Using xhr ETag response header rather than 303 xhr status, since FF returns 200 instead of 304.

  • Jonathan Lister

    Jonathan Lister October 7th, 2010 @ 02:26 PM

    • State changed from “open” to “resolved”
    • Milestone cleared.
    • Milestone order changed from “18” to “0”

    This is presenting me with enough problems to think this is too much of a case of round peg, square hole. The interface wasn't designed to scroll the x-axis markers along without redrawing, and it's proving difficult to add this in. I suggest that the heatmap drawing mechanism is rethought in light of the new decisions about how the heatmap should work, and then we re-write it for 1.0.

    The ETag handling is in place.

  • Ben Hood

    Ben Hood October 19th, 2010 @ 05:53 PM

    • State changed from “resolved” to “closed”
  • Ben Hood

    Ben Hood February 4th, 2011 @ 02:48 PM

    • Milestone set to “0.9.3”
    • Milestone order changed from “3” to “0”

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

A Real Time Differencing Tool.

Shared Ticket Bins

People watching this ticket

Referenced by

Pages