what do you think of naming this endpoint `/graphite_data`?  It doesn't really "poll"...

I like how you generalized how the endpoint is *implemented* but that doesn't preclude us from creating more specific endpoint names that are internally implemented by the same, or similar, code paths (rather than generally named all-encompassing ones).

For example, we could modify behavior based on the path name in the request...  I think this would help cleanup the need to have an update attribute on our HTML elements.  They instead could have a *class* named `rate` which seems more semantically correct.

Let's chat through this on wednesday :)