NYCPHP Meetup

[Allen Shaw]

Chris, what you say is true, but I think Aaron would be okay to show them
what they saw before (exactly what the user saw at the time when  the
resource was retrieved").  Seems like he's trying to prevent them from
having the page reloaded with new information off the server.  Isn't that a
different thing?

- Allen

> With a standards-compliant browser, you shouldn't be able to. As a
> standards-conscious developer, you shouldn't want to.
>
> >From section 13.13 of RFC 2616:
>
>    In particular history mechanisms SHOULD NOT try to show a semantically
>    transparent view of the current state of a resource. Rather, a history
>    mechanism is meant to show exactly what the user saw at the time when
>    the resource was retrieved.
>
> Hope that helps.
>
> Chris