The immediate problem I see with this approach, is that
$Response->LastModified() can only be called once per request. Consider a
situation when a single asp file has multiple includes and each include is
generated from a separate datasource. In this case, each include has to
report back with its own last modification time.
Dmitry
At 11:41 PM 2/13/00, Joshua Chamas wrote:
>\How about some API extension, like $Response->LastModified($time)
>that would automatically check the incoming If-Modified-Since
>incoming header, and if set, and the LastModified time is
>less, than would automatically call a $Response->End() and
>send the NOT_MODIFIED status? There would also be a side affect
>of sending a Last-Modified header if an If-Modified-Since was
>not sent, or if Last-Modified is greater.
