Boris Kraft wrote:
On 09.10.2005, at 03:15, Kyle Gabhart wrote:
In 2.1.1 (nearly final) you will get boosted away ;-)
That's good to hear Philipp. What is the performance boost
attributed to with 2.1.1? Is it a magnolia code change, an updated
JackRabbit release, or a combination of the two? I ask because I am
in the process of modifying 2.1 to fit my company's needs and the
performance boost would be very helpful. If I could incrementally
migrate over the changes that would be much better than having to
rework all the changes once 2.1.1 is available. Can you point me to
the file or files that I need to get from SVN?
As Philipp said, were nearly there. No big changes, its 2.1.1 not 3.0 :-)
So the API is the same, just keep doing what you do and activate to
2.1.1 once its there, and all is fine (fingers crossed)
Okay, so what actually changes? Are there certain classes or taglibs
that change? Is it just changes made to the repository requiring config
file changes and a new repository directory?
The boost compared to 2.0 is from changing our internal node
structure; the boost between 2.1 and 2.1.1 is because we switch the
default repository from file system to BerkleyDB, which is especially
useful in respect to backups.
Great, so how do I retrofit a 2.1 deployment with this? Like my
original post said, I'm in the process of modifying the 2.1 source code
to meet my needs. I just want to know what changes and what doesn't.
Thanks.
-KG
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
