RE: [Avalon4:PROPOSAL] Context Consensus (version 2)
"Berin Loritsch" <[email protected]>
| Newsgroups | gmane.comp.jakarta.avalon.apps.devel |
|---|---|
| Message-ID | <000b01c2a2a7$f3d536b0$df00a8c0__26896.9990699135$1039784540@acsdom1.citius.com> |
> From: Paul Hammant [mailto:[email protected]] > > I'm unhappy with anything other than a base interface (Context) or > specialised interfaces (e.g. BlockContext) being used to descibe > parameter0 of contextualize for the IS-A proposition. Why? K/HC/CAPI > separation; separation of interface and impl etc. As an > advocate of the > BlockContext (and alike) solution I have no requirement for > things like > GenericBlockContext (it was a class not an interface). Could you expand your acronym for me, I am not familiar with it: K/HC/CAPI