Subject: Re: V16 Review - Auditing contexts and their terminations

From: Tom-PT Taylor <[email-masked]>
Date: Thu, 13 Apr 2000 14:12:19 -0500

I've gone back to the original message to keep things simple.  The
introduction of a new command to audit contexts is IMHO an optimization
rather than a bug fix, and cannot be considered for v1 -- could think about
it for v2.

Comments on your specific issues below:

> -----Original Message-----
> From: Greene, Nancy-M [CAR:5N40:EXCH]
> Sent: Thursday, March 23, 2000 12:54 PM
> To:   [email-masked]
> Subject:      V16 Review - Auditing contexts and their terminations
>
> Here are 2 issues with the ABNF that have come up on our review of
> section 7.2.5 AuditValue:
>
> 1) 7.2.5 Audit Value - auditing all matching terminations and their
> contexts
>
> Issue: The entry before the last in table we have
> "ContextID=ALL  , TerminationID= wildcard, Audit of all matching
> terminations and contexts to which they are associated."
>
> Comment: In the ABNF, the reply reads like this:
> AuditValue = contextID { t1,t2,...}
> We can't report all the contexts in this reply.
> The ABNF must be fixed to allow returning list of contexts
> rather than just one with a list of terminations.
        [PTT]
        As I see it, there is no problem here.  You're looking at the wrong
production.  Look at transactionReply and actionReplyList instead.  The
latter allows reporting of a series of action replies, matching the
"ContextID=ALL" specification.

> 2) 7.2.5 Audit Value - return all context ids
>
> Issue: The last entry in the table is:
> ContextID=All, TerminationID=Root, list of all contextIDs,
>
> Comment: The ABNF does not allow a list of contextIDs
> returned on the audit. This has to be fixed to allow list of
> contexts.
        [PTT]
        Same comment as the previous one.  The results are indeed rather
verbose and it would be nice to fix that, but not until v2.

        [PTT]  [snip]