Looking at the case where there is a local change on a PST that needs to
get updated in a PSP, there are two solutions, both supportable by our
draft SPML spec:
1) The PSP discovers the change using an SPML search (reconciliation).
2) The PST acts as client to the PSP (which acts as a server) to send
the change as a modification request (serves as an asynchronous
notification).
I do not believe that we need to add explicit asynchronous notification
operations at this point.
Jeff Bohren
Product Architect
OpenNetwork Technologies, Inc
-----Original Message-----
From: [mailto:]
Sent: Monday, February 17, 2003 10:55 AM
To:
Subject: [provision] missing use cases?
We don't have use cases (nor operations obviously) that address
asynchronous messages from the servers to the clients. For example, a
notification from a PST or PSP to indicate that a service has been
suspended or deleted for some reason other than an add/delete/modify
request.
Is this intentional or an oversight on our part? If intentional, how
would
we address this scenario? Discovery by the client?
Mike Polan
IBM Canada Ltd
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
