RE: OPES protocol, pre-draft 01

At 00:43 27/02/03, Alex Rousskov wrote:
> Do you agree that <xaction-end error> is equivalent to <zap>? Or is
> there more functionality in <zap> that <xaction-end error> is missing
The more you add to <xaction-end error> the more you will make it looking 
it alike at a given time. But the more you add "error" the more you add 
possible error types confusion.
Let settles that <zap> means <xaction-end error nr "zap"> and let 
developpers use it. IMHO thei will result in <zap> being first tested and 
<action-end error nr "zap"> being the default in the action-end case, 
freely tested as per the developper gusto or priorities.
Also <xaction-end error> calls of reread/maintenance of the code when the 
protocol is enhanced and options added. <zap> not.
You will see that "nr zap" will complexify over time, while <zap> will stay 
an immediate clean and reset  command. Are you ok with that?
Anyway in my version there will be <zap> support :-)
Thank you.
jfc