Why implement it in Java? Why not use the faster C or C++? Then, through a Jini interface you could bind it to your Java classes.
Do you have a system running on Prevayler that is actually lacking speed? @;)
Did you take a look at the
ScalabilityTestResults?
Having it all in Java is also Simpler. Using C at some point is something we can keep in mind, though. --
KlausWuestefeld
There are a lot of compelling reasons to NOT use JNI, JINI, CORBA or whatever technology/buzzword you want
Prevayler to be compliant to/support: simplicity.
This stagnates
Prevayler in a way that it's difficult to think of new features, but if making it work with XYZ will not make it faster or simpler or affect scalability in a positive way, then there's no reason to put it into the main code.
I think the most exciting "feature" of
Prevayler - and that is part of the problem it came to solve - was ***SIMPLICITY***. Smile. @:) --
CarlosVillela
As far as I know, Jini adds a significant overhead to method calls. This said, while Jini implementation would be much less simple, it wouldn't necessarily be any faster or could be even slower. Of course it's impossible to say it for certain without trying out, but I don't see much use for these tests unless we start to have serious performance problems with
Prevayler. --
JariJuslin
Did you all mean JNI when you said JINI? Otherwise this makes no sense
--
StephanSchmidt