hi Jonathan and Keith,
as I have already written in this same mailing list I like your proposal
of using Rest
I completely agree with Jonathan that we should follow the same model
that has evolved in the Internet for restful services.
But I think that if we want follow how Internet has evolved or is
evolving we have to do it completely.
unfortunately yesterday I wasn't able to attend the Bliss wg due to the
concurrent OAuth bof,
however I have followed the meeting via the jabber room, and I was the
one asking about the possibility
to at least *investigate* the possibility of use BOSH (
http://xmpp.org/extensions/xep-0124.html ) as a mechanism
to notify the eventual HTTP resource changes as an alternative or in
combination to a new sip event package.*
*Bosh is a protocol that emulates a bidirectional stream between two
entities (e.g. client and server) by using multiple
synchronous HTTP request/response pairs without requiring the use of
polling or asynchronous chunking.
I want to also stress the fact that *Bosh is not part of XMPP*, in fact
BOSH can be used to implement any bidirectional
XML stream transporting a mixture of elements qualified by namespaces.
Bosh is already (largely ?) used in Internet to exchange notifications
between clients and web servers, so it would be interesting
to investigate if we can use it also for our aims.
Of course I am perfectly aware that Bosh is not the only possibility,
and there is also Comet or if you prefer web socket,
however IMO they do not fit so well for our scope as Bosh does.
best regards
/Sal
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
