Re: Flow Layer Database API

2003-03-04 Thread Antonio Gallardo
> Antonio Gallardo wrote: >>>On a personal note, it is unfortunate because I think your new >>>techniques will be more attractive to my Client! Even though it may >>> not be the best way to work, they will find it easier to understand, >>> being closer to what they used to do. So even though I migh

Re: Flow Layer Database API

2003-03-04 Thread Stefano Mazzocchi
Antonio Gallardo wrote: On a personal note, it is unfortunate because I think your new techniques will be more attractive to my Client! Even though it may not be the best way to work, they will find it easier to understand, being closer to what they used to do. So even though I might prefer O-R Map

Re: Flow Layer Database API

2003-03-04 Thread Jeremy Quinn
On Tuesday, March 4, 2003, at 11:10 AM, Antonio Gallardo wrote: On a personal note, it is unfortunate because I think your new techniques will be more attractive to my Client! Even though it may not be the best way to work, they will find it easier to understand, being closer to what they used to

Re: Flow Layer Database API

2003-03-04 Thread Antonio Gallardo
> On a personal note, it is unfortunate because I think your new > techniques will be more attractive to my Client! Even though it may not > be the best way to work, they will find it easier to understand, being > closer to what they used to do. So even though I might prefer O-R > Mapping, I don't

Re: Flow Layer Database API

2003-03-04 Thread Jeremy Quinn
On Monday, March 3, 2003, at 11:52 PM, Christopher Oliver wrote: You know what? You're right. My description below was wrong. What I should have said is that I created a simple _JavaScript_ database API that can be used to implement business objects in JavaScript. PetStore Example I believe if

Re: Flow Layer Database API

2003-03-04 Thread Sylvain Wallez
Christopher Oliver wrote: Antonio Gallardo wrote: Hi Christopher: I think that the point they tried to show us is that the database functions can be an optional part of all the Flow block. I agree because some applications will not need to use databases at all. Yes, clearly, that is the case

Re: Flow Layer Database API

2003-03-03 Thread Christopher Oliver
Antonio Gallardo wrote: Hi Christopher: I think that the point they tried to show us is that the database functions can be an optional part of all the Flow block. I agree because some applications will not need to use databases at all. Yes, clearly, that is the case. However, there isn't yet a me

Re: Flow Layer Database API

2003-03-03 Thread Christopher Oliver
Pier Fumagalli wrote: On 3/3/03 20:57, "Christopher Oliver" <[EMAIL PROTECTED]> wrote: I don't see the point in extending the core functionality of the flow, dealing with cocoon pipelines and requests, when this should be only an "external" layer which can be _easily_ implemented by writing one t

Re: Flow Layer Database API

2003-03-03 Thread Christopher Oliver
Pier Fumagalli wrote: On 4/3/03 0:52, "Christopher Oliver" <[EMAIL PROTECTED]> wrote: You know what? You're right. My description below was wrong. What I should have said is that I created a simple _JavaScript_ database API that can be used to implement business objects in JavaScript. Nononono.

Re: Flow Layer Database API

2003-03-03 Thread Pier Fumagalli
On 4/3/03 0:52, "Christopher Oliver" <[EMAIL PROTECTED]> wrote: > You know what? You're right. My description below was wrong. What I > should have said is that I created a simple _JavaScript_ database API > that can be used to implement business objects in JavaScript. Nononono... Now I don't get

Re: Flow Layer Database API

2003-03-03 Thread Pier Fumagalli
On 3/3/03 20:57, "Christopher Oliver" <[EMAIL PROTECTED]> wrote: > I've just committed [experimental] changes that provide a simple > database API for the Cocoon flow layer modeled after JSTL > (http://java.sun.com/products/jsp/jstl). This will allow you to perform > a database query in a flow scr

Re: Flow Layer Database API

2003-03-03 Thread Christopher Oliver
You know what? You're right. My description below was wrong. What I should have said is that I created a simple _JavaScript_ database API that can be used to implement business objects in JavaScript. This really has nothing to do with the "flow" layer per se, which is about controlling page flo

Re: Flow Layer Database API

2003-03-03 Thread Gianugo Rabellino
Christopher Oliver wrote: I've just committed [experimental] changes that provide a simple database API for the Cocoon flow layer modeled after JSTL [...] Let me know what you think. OK, first of all I must confess that I have little or no experience with the flow, so probably I should just sh

Re: Flow Layer Database API

2003-03-03 Thread Christopher Oliver
Sylvain Wallez wrote: Christopher Oliver wrote: The cocoon object now supports a new function getConnection([String] dataSourceName); This looks cool... but, continuing my rant about oversimplification, why does the _cocoon_ object hold methods to access database connections ? AFAIK, this

Re: Flow Layer Database API

2003-03-03 Thread Sylvain Wallez
Christopher Oliver wrote: I've just committed [experimental] changes that provide a simple database API for the Cocoon flow layer modeled after JSTL (http://java.sun.com/products/jsp/jstl). This will allow you to perform a database query in a flow script that produces a bean-like object for us

Re: Flow Layer Database API

2003-03-03 Thread Tony Collen
On Mon, 3 Mar 2003, Christopher Oliver wrote: > I've just committed [experimental] changes that provide a simple > database API for the Cocoon flow layer modeled after JSTL > (http://java.sun.com/products/jsp/jstl). This will allow you to perform > a database query in a flow script that produces a

Flow Layer Database API

2003-03-03 Thread Christopher Oliver
I've just committed [experimental] changes that provide a simple database API for the Cocoon flow layer modeled after JSTL (http://java.sun.com/products/jsp/jstl). This will allow you to perform a database query in a flow script that produces a bean-like object for use by your presentation laye