RE: [security-services] Core 26

[Scott Cantor <cantor.2@osu.edu>]

> PS: Given the choice I'd personally dump the entire, IMO way 
> over-complex, status stuff from lines 1101-1199 and keep the 
> 19 lines from 1200-1219. 200 vs 20 lines of spec, who knows how 
> many LOC, is a no-brainer for me unless status handling is a 
> major customer requirement, which I don't believe is the case. 
> However, that's just me:-)

If you can demonstrate how a simple, unextendable enum is sufficient to
build any real applications on top of this protocol, I'm certainly open.
The mandatory processing model is identical in both cases (examine the
top code, ignore everything else if you want), so the complexity is all
optional.

-- Scott