On Nov 19, 2008, at 1:18 PM, Alan Johnston wrote:
One consequence of this, pointed out by Dale Worley, is that the
Appearance Agent must be prepared to handle all SUBSCRIBEs and
PUBLISHes for the dialog events for this AOR, not just the ones used
for implementing shared appearances. Since the Appearance Agent is
essentially just a state agent that also inserts additional
information about appearances, this should not be a problem. We
need to give this a little more thought to make sure this is
reasonable and does not cause problems for proxy routing logic.
In addition, the draft needs to have some text clearly describing
this and Dale has volunteered to submit some.
Why does this draft need to call this out? This is standard behavior.
Do we really think that somebody is ever going to have two state
agents with one for dialog events and one for dialog events
originating from shared appearances? If that was the case, we wouldn't
use dialog event for SA.
Jason
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
