Eric Webb wrote:
Since moving to web application frameworks (jakarta turbine and ww2)
I've exclusively used velocity. I find velocity's syntax to be simple,
clean, and sufficently powerful for constructing views. I mean, when
you get down to it, a view is simply html (in most cases), and
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, February 22, 2004 11:11 AM
Subject: Re: [OS-webwork] Velocity vs. JSP
Eric Webb wrote:
Since moving to web application frameworks (jakarta turbine and ww2)
I've exclusively used velocity. I find velocity's syntax to be simple,
clean
Rickard Öberg wrote
...
2) Great performance
3) Templates does not have to be in files (JSP files do)
...
where does the performance win over JSPs come from? As JSPs are compiled
into servlets, how do you beat that?
if you don't put your templates into separate files, then where do you
put
--- Erik_Jõgi [EMAIL PROTECTED] wrote:
Rickard Öberg wrote
...
2) Great performance
3) Templates does not have to be in files (JSP
files do)
...
where does the performance win over JSPs come from?
As JSPs are compiled
into servlets, how do you beat that?
Did you looked into
remigijus wrote:
Ok it sounds nice, I'm not against velocity, I'm just curious.
How many hits you are getting per day and peak load?
What hardware and software do you use?
We do load tests sometimes, but it's hard to compare that with reality.
In reality, we do have one web hotel server which
Erik Jõgi wrote:
Rickard Öberg wrote
...
2) Great performance
3) Templates does not have to be in files (JSP files do)
...
where does the performance win over JSPs come from? As JSPs are compiled
into servlets, how do you beat that?
Don't know, don't care. It's just faster :-) That's probably not
- Original Message -
From: Rickard Öberg [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, February 22, 2004 6:27 PM
Subject: Re: [OS-webwork] Velocity vs. JSP
remigijus wrote:
Ok it sounds nice, I'm not against velocity, I'm just curious.
How many hits you are getting per day
rendering. The if and foreach
constructs seem much more intuitive than their tag-based counterparts in
JSP.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hani
Suleiman
Sent: Sunday, February 22, 2004 8:25 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork
Hello,
Following the 'Tomcat out of memory' thread in this list I got the
impression that several people were suggesting to Velocity instead
of JSPs for for the views.
I haven't got any experience with Velocity besides looking at the
stuff that is part of WebWork but for some reason I have
Robert Nicholson wrote:
Is this the same SiteVision that's on SourceForge?
Nope. It's a closed-source product from my new company, Senselogic.
/Rickard
--
Rickard Öberg
[EMAIL PROTECTED]
Senselogic
Got blog? I do. http://dreambean.com
Heh, this thread sure did mutate today. Am I on TSS? :-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Mike Cannon-Brookes
Sent: 10. desember 2002 02:55
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Velocity or JSP?
Aslak,
Having just
- Original Message -
From: Aapo Laakkonen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 3:07 AM
Subject: RE: [OS-webwork] Velocity or JSP?
I'm about to start a new project, and we have decided
to use WebWork. I'd like to hear what kind of view
technology the WebWork
Aslak,
Having just written a book chapter on WebWork views, I'm quite au fait with
this situation! :)
The JSP views _are_ more advanced at the moment, but that's only because
none of the core developers has any Velocity projects or much Velocity
experience. There is no reason (from looking at
13 matches
Mail list logo
