cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Burton <>
Subject Re: XObject
Date Sun, 03 Dec 2000 21:41:25 GMT
Robin Green wrote:

> >Nice idea, but XObject is an interface. To change it to a proxy, you
> >have to make it a class, thus inevitably breaking existing code. To
> >avoid that while preparing the C1->C2 transition, I think it's better to
> >have a new clean SAX2 compliant XObject (X2Object ?) and deprecate the
> >old one. This will warn current C1 users that they should migrate to
> >X2Object to be compatible with C2 while allowing them to keep their
> >current code unchanged if they want to stay with C1.
> +1.

It's an interface? Oh yeah...  :-)  X2Object? XObject2?  XObject-TNG? 
Whatever it's called, I'm +1 for a new implementation and the
appropriate warnings to the error log if the old one is used.

Ross Burton

View raw message