Re: Reflection on Jar NOT in Classpath?
Twisted wrote:
Andrew T. writ:
(code, jars, ..stuff)
...may be stored as a (whadda'ya'callit?) BLOB in the
DB.
Some databases can in effect be accessed via a URL. Those backing Web
servers come to mind. :)
URL's are wonderful things, for getting at resources. :-)
...
Another thing to note is that the next generation of filesystems is
likely to be built on full-blown ACID database logic, ...
"Atomicity, Consistency, Isolation and Durability"?
Sounds good to me - and a lot more than my current
FS offers.
...
Regardless, I can tell you right now that even the venerable NTFS is
showing age and creaking under modern loads of millions of files,
hundreds of gigs, and really long paths and file names to keep all
those millions straight. ...
As someone who has lost entire NTFS filesystem(s),
I actually cringe as I read that.
...
In light of capabilities like these, and consistency/transactional
integrity/scalability advantages, filesystems like this seem
inevitable; it's only a matter of time ..
Time?! It's over-bloody-due, if you ask me!
...and research.
...
Then loading classes from a database will be routine, and loading
classes NOT from a database will be unusual!
Give me a full RDB file system, with those
qualities you mentioned above, and I'll be
happy ( at least with the FS ;).
--
Andrew Thompson
http://www.athompson.info/andrew/
Message posted via JavaKB.com
http://www.javakb.com/Uwe/Forums.aspx/java-general/200707/1