"Hastings, Tom N" wrote:
> ...
> 4. Which leaves how to indicate that this is really the last response,
> i.e., that there are no more Subscription objects left that match? Marty
> Joel suggests that there be a completely separate response part with its
> own status code. The status should be the 'client-error-not-found' which
> is the status returned when there are no Subscription Objects found,
> whether this is the first Get-Notifications response or the last.
This will work, although it won't indicate if the subscription has run
out or just been cancelled, and it doesn't cover the situation if you
do a Get-Notifications with wait=false - i.e. you are only getting a
single part, and there are events, but how do you know if you need to
ask again?
How about adding a status code called
"successful-ok-subscription-expired", which will be returned by
Get-Notifications when the subscription has no more events and has
expired?
That way if a subscription is cancelled *while* a client is waiting
on more event messages, the client will see a different status code
(client-error-not-found) and can display a suitable error/warning
message, vs. seeing that a job has completed because of the
"successful-ok-subscription-expired" status?
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw.com
Printing Software for UNIX http://www.easysw.com