2008/11/20 Adam Roach <[EMAIL PROTECTED]>: > Any feedback you have is welcome.
Adam, It's great to see work on this. After a quick glance over the document, a few comments: It would be good to explicitly mention that you could also use a <link rel="monitor"/> element within <head> of an (X)HTML document, and <atom:link rel="monitor"/> within an atom entry element, too. One thing i have been thinking about is monitoring multiple HTTP resources on the same (logical) server. In a number of places this mechanism is useful, a number of subscriptions to the same server would be common. It would be nice if there was a way of being able to collect a number of HTTP URI's and monitoring them all in one subscribe, assuming they are all on the same server (Which could be calculated somehow). My initial thoughts were along the line of separating the SIP URI for monitoring and a document identifier - then allowing the SUBSCRIBE to contain the list of document identifiers that you want monitoring (perhaps via an XML body). Also, The SUBSCRIBE should pass the ETag it received when it fetched the document, so there is no race condition between a GET/HEAD and the subscription being processed by the SIP server - if the ETag has already changed when the SUBSCRIBE is received, a NOTIFY can be sent out immediately. ~ Theo -- Theo Zourzouvillys Chief Technical Officer VoIP.co.uk - Commerce House, Telford Road, Bicester, OX26 4LD Tel: +44 1908 764 196 _______________________________________________ BLISS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bliss
