> > 1- I am a bit skeptic about pure pull;
>
> Why?
>
> -jon
I'm just skeptic about using pure Pull 100% of the time.
So, it is not a black or white issue for me. But pursuing a single
way of doing something doesn't usually work. Some systems work most of
the time, but not all of the time. Just one of those 80%/20% things.
Advantage of _trying_ to use pull all the time:
When you miss functionality you can't easily put in the template,
you add something to your infrastructure/framework in a reusable
way. And this means you keep improving the functionality of your
framework in a more reusable way than doing it to be used just once
in a Servlet or JSP.
OTOH, sometimes what you do is so unique that there is more cost than
benefit in trying to produce a purely PULL solution.
I am skeptic about many other "pure" solutions too. Like, for instance,
using Velocity to convert a dataset into XML (in the way that Oracle's
XSU library does it) or into a tab delimited format. Velocity is the
best way of generating most formatted text outputs (like web pages) I
get across, but not all of them.
So, I try to use pure PULL for most of my pages, but not for all of
them.
Have fun,
Paulo Gaspar
P.S.: Big answer for such a short question, huh?
Why could just have written "Why not?"
=;o)
> -----Original Message-----
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 05, 2001 19:00
> To: [EMAIL PROTECTED]
> Subject: Re: [PROPOSAL] InsertionListener
>
>
> on 4/5/01 7:34 AM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote:
>
> > 1- I am a bit skeptic about pure pull;
>
> Why?
>
> -jon
>
> --
> If you come from a Perl or PHP background, JSP is a way to take
> your pain to new levels. --Anonymous
> <http://jakarta.apache.org/velocity/ymtd/ymtd.html>
>
