Future Prevayler

In fact, it looks like bytecode instrumentation can allow .journal
files to be written from there, so a future version of Prevayler might
allow you never have to stray from your original object. i.e. one line
e.g. Prevayler.prevail(myObject); recovers/persists to/from that
object, nothing else necessary. If possible and combined with the disk
thing it'll be the ultimate Java persistence engine by far in every
situation (only surpassable if Oracle makes it native to Java, but
that would destroy all of their own database products). It'll probably
be that so far with the disk thing alone.

> Looks possible via bytecode instrumentation even after the jvm has started:
> http://download.oracle.com/javase/6/docs/api/java/lang/instrument/package-summary.html#package_description
> http://www.csg.is.titech.ac.jp/~chiba/javassist/
>
>> ...so you could seamlessly create and use terabyte+ sized Java objects with it!
>>
>> Stupid? Crazy? Pointless? Impossible? Maybe one day? Or already possible?
>>
>> Maybe by transparently allowing deserialization/serialization of
>> fields to/from memory, based on which ones are most/least used. Or
>> maybe there's an even simpler way.
>>
>> I'm guessing it'd still be way more performant than databases. I like
>> the Prevayler "way" of doing things, so I wouldn't want the user code
>> to change in any way, so it'd still be "Prevayler".
>>
>

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org