On 11/21/08 2:07 AM, Theo Zourzouvillys wrote:
On Fri, Nov 21, 2008 at 4:12 AM, Adam Roach <[EMAIL PROTECTED]> wrote:
Very interesting proposals. Admittedly, for the use cases SIP is most
interested in, the results are not typically HTML, but the idea of
communicating these in the body may have merit. I'm curious about which use
cases you have in mind -- do you imagine that there will be circumstances
under which the HTTP server will have the ability to notify other nodes of
changes, but not have the ability to include a Link: header?
absolutely - perhaps a resource hosted on a CDN, where you commonly
can not send custom headers.
or a blog, which may be hosted on some other platform (for example,
blogger.com) where you can edit the HTML but not the headers.
I understand the difficulty in putting new HTTP headers into responses
under such circumstances... but I also don't understand how you'll
provide notification of changes under such circumstances either. Do you
envision that people publishing via a CDN or a blog will turn around and
manually kick a SIP server to cause it to send notifications?
The issue I'm having is that it seems a bit contrived that anyone
publishing under the relatively constrained circumstances you describe
will nonetheless have access to a SIP events server that provides
notification for such changes -- but that could just be a lack of
imagination on my part. Can you expand your use-case to tell a story
about where these people are getting their SIP event servers (are they
hosted?) and how the SIP event server finds out about changes to the
HTTP server.
the Link header as defined in draft-notthingham-http-link-header
itself is only a way of representing the <link> header in HTML and
<atom:link/> header in atom entries outside of the content where it is
not possible because the content-type does not have support. So it
already "just works" by creating a link registry entry, however would
be good to explicitly point out that it could be anywhere a link
relation is allowed.
That's interesting -- Mark, do you have any input on the topic?
/a
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
