Semi-Newbie. Is newapp push or pull?

[Bill Holloway <ho...@io.com>]

I read Jon Stevens Push v. Pull article and have been through some of the
newapp source that ships with the current tdk download.  I still can't   
really tell if this uses the push or pull model.  Thanks.

Bill


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

ant init errors

[Naga Pappireddi <na...@jalvamedia.com>]

Hello,
We defined db xml schema in which we extended TURBINE_USER to have more
fields  and being accessed thru MAM_USER as alias. During ant init I get the
following errors. Obviously this sql is generated from xml schema and has
some FK issues. I am wondering what these msgs mean and how I can fix the
xml schema to avoid this. The functionality is not affected but I am
concerned that this is something I should avoid(much like C compiler
warnings being potential runtime errors)

Thank you in advance

Naga



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Semi-Newbie. Is newapp push or pull?

[Mark Nutter <ma...@zoominternet.net>]

On Sun, 2002-05-05 at 17:27, Bill Holloway wrote:
> Gulp.  OK.  That steepens the learning curve -- maybe -- I was wondering 
> what all the "Flux" stuff was.
> 
> Are there any users of this "mixed" model out there who have an opinion on 
> its stability/usability?  Thanks.

It's very useful, but each model has its place.

Push model:  I have a Java class tied to a particular screen (or
layout), and the Java class pushes the data to that particular
screen/layout.  The data is available only to that particular screen. 
Good for special purpose applications, e.g. restricted-access admin
functions.

Pull model:  I have a Java class that creates data that might be useful
on any number of arbitrary pages, and I can include that data on any
screen or layout I want.  The nice thing about pull model is that you
can define dynamic data, and make it available to less-technical
designer types, without having to know or care which screen or template
it appears on.  For example, if you have a Localinfo pull service that
defines a time(), date() and weather() method, you can tell your HTML
pushers that they can easily include dynamic time, date, and weather
info in their pages just by inserting tags that say

$localinfo.time()
$localinfo.date()
$localinfo.weather()

They can put that much on a 3x5 card, and then design the web site
however they like.

The difference between push and pull is strictly a matter of how the
dynamic objects get put into the Velocity context.  In the push model, a
screen-specific or layout-specific class puts the dynamic object into
the context for that particular screen/layout.  In the pull model, the
pull service put the dynamic object(s) into the Velocity context of all
screens and layouts.  In fact, the pull service puts the objects into
the contexts of screens and layouts that have push-model objects, so if
you have a screen that uses the push model, you can use both push and
pull in the same screen.

Caveat:  I'm still learning Turbine, so if I'm misrepresenting
something, feel free to correct me, but I believe that's correct.

Mark Nutter
manutter@zoominternet.net


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Semi-Newbie. Is newapp push or pull?

[Bill Holloway <ho...@io.com>]

Gulp.  OK.  That steepens the learning curve -- maybe -- I was wondering 
what all the "Flux" stuff was.

Are there any users of this "mixed" model out there who have an opinion on 
its stability/usability?  Thanks.

Bill

On Sun, 5 May 2002, Stéphane MOR wrote:

> Bill Holloway wrote:
> 
> >I read Jon Stevens Push v. Pull article and have been through some of the
> >newapp source that ships with the current tdk download.  I still can't   
> >really tell if this uses the push or pull model.  Thanks.
> >
> [ I don't know which version you are using . I will talk about the tdk 
> in Turbine 2.1.]
> 
> Actually, it uses both !
> There is a Service called TurbineService (push model).
> Then the code from this Service is called from an ApplicationTool (pull 
> model),
> under org.apache.flux.tool.FluxTool.
> You then use this tool in your templates, using $flux.Whatever.
> 
> Here you are ! ;-)
> Stéphane
> 
> >Bill
> >
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
> 

-- 
"They willingly traded everything they owned.... They do not bear arms,
and do not know them.... With fifty men we could subjugate them all and
make them do whatever we want."

     -- Christopher Columbus' log entry regarding the Arawak people
        whom he encountered upon arriving in the Americas, 1492


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Semi-Newbie. Is newapp push or pull?

[Stéphane MOR <st...@yahoo.fr>]

Bill Holloway wrote:

>I read Jon Stevens Push v. Pull article and have been through some of the
>newapp source that ships with the current tdk download.  I still can't   
>really tell if this uses the push or pull model.  Thanks.
>
[ I don't know which version you are using . I will talk about the tdk 
in Turbine 2.1.]

Actually, it uses both !
There is a Service called TurbineService (push model).
Then the code from this Service is called from an ApplicationTool (pull 
model),
under org.apache.flux.tool.FluxTool.
You then use this tool in your templates, using $flux.Whatever.

Here you are ! ;-)
Stéphane

>Bill
>


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>