on 8/9/01 6:50 AM, "Finn Smith" <[EMAIL PROTECTED]> wrote:

> A question for those who have a good grasp of the current state of Pull
> tools and Intake in the Turbinen project:
> 
> I've taken a look at the Scarab code, the documentation for the Pull tool
> service, and the Intake tool service. It seems the use of the Intake tool
> with actions and a request scope Pull tool (a la Scarab) is a clean way to
> implement the MVC model.
> 
> However, I do have a few questions about this. The note at the top of the
> Intake service page says that Intake "is currently beta quality software and
> that it is still undergoing development and debugging." and "quite a few
> bugs and modifications have been made to Intake since it was released with
> 2.1."
> 
> I'd prefer to stick with a stable version of Turbine/TDK (2.1). Does it make
> sense for me to use the Intake tool implementation which comes with 2.1? Or
> is it too buggy?

That is why the quote is at the top of the page. I could simply re-quote the
quote or you could just believe what it says. :-)

> If Intake in 2.1 has too many problems, does anyone know of
> a clean way to implement the MVC model, using the Pull tool, *without* using
> the Intake tool?

Pull != Intake

Intake is simply an implementation of a Pull Tool.

The Pull Service itself should be pretty stable in 2.1. I don't know of any
real issues with it. It is pretty simple.

> At this point it seems like my two options for Intake are:
> - stable 2.1 Turbine with buggy Intake   OR
> - buggy Turbine CVS-HEAD with less buggy Intake
>
> Is this true?

Yes.

The CVS-HEAD isn't really buggy perse. It is under near-daily modifications
which are not always backwards compatible and sometimes very hard to keep up
with.
 
> I'd like to have a working beta/prototype of the webapp I'm working on by
> the end of August, so what's my best bet for getting started working on this
> right away?

That is really up to you...

-jon


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to