>What would you propose a servlet container do when a page has three >different includes, each of which wants to set the same header to some >different value? Remember that, as far as the client is concerned, this >is a single request, so there is no such thing as a "last modified" >timestamp for only part of the page.
I would suggest that the "last one to write the header wins."... right up until the point that the page gets returned to the browser, any part of the complete page (including includes) should be able to modify any header info, and simply the last one to write info "wins." It would of course be up to the developer to design an intelligent page so that the wanted results are obtained... but with the current API, we developers have NO WAY to do this without resorting to "@" includes, which have their own terrible problems... Jim -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
