You are right, I did mention persistent search. This is a concept
from the LDAP work, whereby a client can post a query that does
not terminate after the original results are returned; instead new
(or modified) entries that satisfy the search query will be returned
on an active channel (see draft-smith-ldap-psearch-00.txt).
This was mentioned not as an existing notification mechanism, but
as an alternative design to the normal asynchronuous notification
schemes (where the "notification server" contacts the "notification
client" to send the event). In the persistent search case, there
is an active channel between the server and the client (along the
lines of the HTTP connection discussion that has been going on
in the IPP DL).
As we discussed in Maui, and as Jay has already mentioned, this
alternative is not scalable, as resources are consumed for each
active connection. But it is some nice food for thought.
...walker
-- Jim Walker <walker@dazel.com> System Architect/DAZEL Wizard DAZEL Corporation, Austin, TX