On Tuesday 06 January 2004 23:22, Berin Loritsch wrote:
In order to solve "model" issues much easier and much more flexibly, I
propose to use the work that Leo did a while back with the Attributes
embedded in the class file itself.
Without knowing too much (as usual) about the subject, I would ask "Is it that clever to 'roll your own', instead of awaiting the JDK1.5 in a couple of months?"
If one can't wait for 1.5 to be available to all platforms, would it still not make sense to "wait" and keep what we have meanwhile?
I've discussed this with Leo before. Basically, what we want to make sure is that the runtime api is completely interface-based and completely non-intrusive. That way, once jdk 1.5 comes out, it should be possible to create a seperate version of the attributes runtime api that utilizes the jdk 1.5 attribute support.
Just like we did with logging, regular expressions, non-blocking I/O, etc.
The tricky part is figuring out what exactly jdk 1.5 will support.
Note this principle applies whether we stick with "what we have" or a migration to any different package is done.
-- cheers,
- Leo Simons
----------------------------------------------------------------------- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles & Opinions -- http://lsd.student.utwente.nl/jicarilla/Articles ----------------------------------------------------------------------- "We started off trying to set up a small anarchist community, but people wouldn't obey the rules." -- Alan Bennett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
