On 2012-03-08 20:25, Christian Schmidt wrote:
...
Separating the network protocol from the user interface seems highly
desirable. Window-Target sacrifices that.
I get your point. But it seems that Content-Disposition already suffers
from this.
RFC 2183 describes the Content-Disposition like this:
A mechanism is needed to allow the sender to transmit this sort of
presentational information to the recipient; the Content-Disposition
header provides this mechanism, allowing each component of a message
to be tagged with an indication of its desired presentation semantics.
I know that RFC 2183 deals with e-mail and is not pat of HTTP/1.1, but
it is mentioned in the HTTP specification and is supported by several
browsers.
...
Content-Disposition for HTTP is defined in RFC 6266.
...
Best regards, Julian
