what? no 304???
what a shift in perspective! since i've been spending so much time with HTTP/REST constraints, i've discovered a shift in my perspective when it comes to defining and implementing web applications. the most recent example is my attribute about the
HTTP Status 304
i learned today - while implementing a simple resource pattern - that i might not be able to reliably track and generate
HTTP 304 headers for GET requests. in the past, i'd write it off as a 'casualty of design' - too bad. but now, i don't like the idea one bit!
now, i want *all* my resources to be able to support
304 and other scalability elements of the REST constraint. now i want it done right - all the time [grin].