thanks greg for sharing my point of view :o) > JDBC might need some weaking too,
my goodness... I meant TWEAKING of course. sounds like "JDBC needs *weakening*" and of course the opposite is true ;o) nevertheless, I never worked on another platform where you needed only one single driver for any database, regardless of the OS (which counts only for type 4 drivers of course) I forgot to add: I find it even quite reasonable to use java/bytecode-to-native-compilers on certain platforms where this is applicable. the code base stays the same nevertheless. there is only one caveat in that case: the dynamic class loading ability has to be maintained! this basic java paradigm must not be broken by such technologies, because otherwise one of the major strengths of JAVA will be relinquished. there are java-to-native-compilers on the market that allow dynamic class loading of not-natively-compiled classes (i.e. bytecode) and therefore fit that demand. just my 2 cents ;o) -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte l�cheln! Fotogalerie online mit GMX ohne eigene Homepage! --- You are currently subscribed to jdjlist as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] http://www.sys-con.com/fusetalk
