Re: Schema provider/CA lookup status

On Fri, 2006-07-28 at 08:52 +0100, Martin Aspeli wrote:
> Roché Compaan wrote:
> 
> > Lovely! Very nice and simple. I also like the name change from Variable
> > to Extensible.
> 
> Bear in mind it's slightly different - it uses an adapter to 
> ISchemaExtender to extend the schema. This is meant to let third party 
> products plug in new schema elements. It doesn't really handle the case 
> when the schema is changed TTW, for example (which ATSENG does, though). 
> Still, if you want a different algorithm inside the Schema() method, it 
> should work the same.

I would probably just override the Schema() method on classes that need
ATSENG, or have a mix in class for schemas that need to be managed TTW.

> The other difference of course is that you have to fire an event to 
> invalidate the schema.

This is what I was referring to when saying "nice and simple". Z3 events
makes it easy to do the cache invalidation, whereas doing this without
Z3 events will lead to a clumsy injection of cache invalidation method
calls in existing schema editing methods.

-- 
Roché Compaan
Upfront Systems                 http://www.upfrontsystems.co.za


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV