geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Blevins <david.blev...@visi.com>
Subject Re: API and serialization compatibility, was: Build Failure
Date Mon, 16 May 2005 15:16:31 GMT
On Sat, May 14, 2005 at 04:00:53PM -0700, Jeremy Boynes wrote:
> David Blevins wrote:
> >On Sat, May 14, 2005 at 09:47:31AM -0700, Jeremy Boynes wrote:
> >
> >>David Blevins wrote:
> >>
> >>>
> >>>Paying attention is an understatement.  In order to serialize
> >>>data to and from class definitions, those classes cannot change
> >>>in any significant way, ever.  No refactoring, repackaging,
> >>>reorganizing, no removing methods, no removing class variables.
> >>>This doesn't just apply to public APIs, but even the internal
> >>>classes of each component.
> >>>
> >>
> >>In other words, the level of stability users expect from 
> >>enterprise-grade software.
> >
> >
> >I can't argue with you there.  Code not changing significantly from
> >release to release is the ultimate of stable....
> >
> >Who needs bug fixes and optimizations anyway ;-)
> >
> 
> I would not classify "refactoring, repackaging, reorganizing, [no] 
> removing methods, [no] removing class variables" as "bug fixes and 
> optimizations", but heck, I only want it to work reliably.
> 

I only want it to work reliably.  As bug fixes and optimizations change the class files from
version to version, they are not reliable formats for configuration storage across upgrades.

Enterprise users need configuation information to be more reliable than class definitions.

-David

Mime
View raw message