> Yeah, I thought that we were going to "bite ourselves in the foot" as
> well. Rewriting code is a pain to begin with and we wouldn't have
> went ahead with the project if it hadn't been for the weblogic staff
> recommending that we remove kona.
>
> We have also tested the code without the kona and seen significant
> speedup.
Again, I think it is something other than the Kona issue. What JVM are you
using? Have you tried switching to HotSpot or Java2 Solaris Production
Release? Both have GC implementations that are much better. Like I said
before, I have developed a complex database application using it entirely
and it performs just fine. What sort of profiling have you done on your
code?
> ECS was looked at as an alternative but it was harder to read than
> kona and we couldn't find any document on it's benefit over kona.
I'm not quite sure what you mean by "harder to read" since we use a lot of
the exact same method names. Your feedback on this would be appreciated. I
have used HtmlKona quite a bit and ECS was developed specificially to be
easier to read and less typing than HtmlKona.
As far as documentation is concerned regarding the benefits, why didn't you
bother to just ask on the ECS mailing list? This is the first time I have
heard of someone even questioning this. Fyi, one major benefit over HtmlKona
is the automatic filtering of Html Entities as well as the ability to define
your own custom filters. You also get source code so that if you need speed
improvements, feel free to add/remove whatever you want.
-jon
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html