I think we can all agree that the storing of a deployment unit using
object serialization is a great optimization that helps startup times.
But we are also finding out that it's causing the sever developer some
pain. Would it be possible to make the object serialization optional?
Regards,
Hiram
On May 14, 2005, at 7:00 PM, 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.
--
Jeremy
