Hi,
I posted a message on the velocity dev list discussing
the approach of a 0.5 velocity milestone and the
hopeful announcment of the velocity service in
turbine.
The code for the actual service itself is complete:
John has had that working for over a week now, but
there are a couple of issues that need to be worked
out in velocity before the official announcment can
be made.
The first problem is an initial startup problem, it
seems upon initial bombarding velocity just plain
screws up. But if you give it a breather it performs
amazingly well. In my primitive testing environment
I have consistently beaten WM by at least 20%, sometimes
this number approaches 30% _after_ the first hit.
I would like the choice for turbine users to be
simple in that velocity is the clear winner in
terms of performance and ease of use. If anyone
in this group could lend a few eyeballs to try
and find this startup problem I would greatly
appreciate it. It would mean that I could make
an official velocity service announcment, and
torque could be switched over to use velocity.
I have checked in all my code from the last
few days, so if anyone can afford to poke
around for a bit it would help get the next
release out a bit faster. If you can take a
poke at it, I'm usually in the chat room at
cvs.working-dogs.com:6667, or you can post
a message to the velocity dev list and I will
respond to any queries ASAP. Or you can send
me email privately.
Thanks,
jvz.
---
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
