On Fri, Oct 31, 2008 at 3:00 PM, Salvatore Loreto <[EMAIL PROTECTED]> wrote:
> About the Theo question on "how using REST for notifications of changes to > resources in a scalable way that works behind NAT" > IMO the more natural way is go for BOSH ( > http://xmpp.org/extensions/xep-0124.html ) > and not for XMPP. > COMET could be another possibility but I think it is too heavy. well, the way i've split up the work is by defining a document for the REST framework itself which makes defining profiles very easy, but left monitoring out of it. There is then a separate document for monitoring of the HTTP resources - I've done some initial work [1] on a interface for monitoring HTTP URI's over a SIP event package, although other protocols could also be defined in the future (e.g XMPP, COMET, BOSH, AMQP). The reason for working on a SIP event package for notifications was that the use cases within bliss most commonly involve running on a SIP UA - although by splitting it out of the main document others can be added as there is the need. ~ Theo 1 - note, I did say "initial" :) - http://dev.voip.co.uk/~theo/ietf/draft-zourzouvillys-bliss-http-uri-monitoring-00.txt - i will try to spend some more time on it soon. -- 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
