[email protected] wrote:
Another solution to this is:
Formulate the state of the queue as a list of the entries in the queue,
each containing identifying information and an indicator for whether it
is "active".
Then have a default filter for "normal" subscribers that only allows
them to see entries for themself.
As a result, normal subscribers will get an initial notification with
their own entry, indicating "inactive". Then they will get no further
notification until the part of the state visible to them changes, which
is when they become "active".
More "privileged" subscribers might be able to see the complete list.
Thanks,
Paul
Hi all,
Perhaps there is a misunderstanding. The caller subscribes to his own CC
state which is a combination of the caller's position in the queue and
busy state of the callee.
You say that, but I don't see anything in the draft supporting it.
That would imply that each caller is subscribing to a *different*
resource. But the procedures for identifying the resource to subscribe
to don't differ from caller to caller. So AFAICT all the callers end up
subscribing to the *same* resource.
That is why Dale and I are trying to create a mechanism/rationale for
why the subscribers don't all see the same results.
Thanks,
Paul
Therefore it is valid that several callers receive the "queued" state at
the same time, but of course only on caller is notified about the
"ready" state per time.
Best Regards
Roland and Martin
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
