On 23.Jun.2003 -- 05:30 PM, Stefano Mazzocchi wrote:
> on 6/22/03 5:06 AM Christian Haul wrote:
>
> > Although I don't like to mention it, action are dual use and by removing
> > special support and restricting access to non-sitemap components they
> > are completely banned.
>
> Yes, that's th
On 24/06/2003 0:25 Stefano Mazzocchi wrote:
(2-mail-pattern, let's hope it works)
I was suggesting we remove it from the FOM as I see no reason to connect
sitemap programmatic artifacts in the flow realm. Read the title, it
starts with [flow], is the context clear enough?
Yes. I'm very sorry to h
on 6/22/03 5:06 AM Christian Haul wrote:
> Stefano Mazzocchi wrote:
>
>>on 6/20/03 2:01 PM Christian Haul wrote:
>>
>>>Reinhard Pötz wrote:
>
>
**
* Component loading *
*
on 6/22/03 3:07 AM Steven Noels wrote:
> On 22/06/2003 8:56 Upayavira wrote:
>
>
>>Just to clarify - Stefano was only suggesting removing input/output
>>modules from FOM, not Cocoon or the sitemap (where they are
>>appropriate).
>>
>>Do your comments still stand?
>
>
> If that was what he was
> From: Steven Noels [mailto:[EMAIL PROTECTED]
> On 22/06/2003 6:01 Stefano Mazzocchi wrote:
>
> > Both actions and input/output modules were created to
> overcome sitemap
> > programmability limitations. Flow doesn't have those limitations
> > anymore so i don't see the reason to keep those
Stefano Mazzocchi wrote:
on 6/20/03 2:01 PM Christian Haul wrote:
Reinhard Pötz wrote:
**
* FOM (Flow Object model)*
**
Context object
--
Stefano Mazzocchi wrote:
on 6/20/03 2:01 PM Christian Haul wrote:
Reinhard Pötz wrote:
**
* Component loading *
**
I see two different ty
On 22/06/2003 8:56 Upayavira wrote:
Just to clarify - Stefano was only suggesting removing input/output
modules from FOM, not Cocoon or the sitemap (where they are
appropriate).
Do your comments still stand?
If that was what he was aiming at, I stand corrected. Although I must
admit that his remar
On 22 Jun 2003 at 8:56, Steven Noels wrote:
> On 22/06/2003 6:01 Stefano Mazzocchi wrote:
>
> > Both actions and input/output modules were created to overcome
> > sitemap programmability limitations. Flow doesn't have those
> > limitations anymore so i don't see the reason to keep those
> > artif
On 22/06/2003 6:01 Stefano Mazzocchi wrote:
Both actions and input/output modules were created to overcome sitemap
programmability limitations. Flow doesn't have those limitations anymore
so i don't see the reason to keep those artifacts here.
What do others think about this?
I think the current c
on 6/20/03 2:01 PM Christian Haul wrote:
> Reinhard Pötz wrote:
>
>
>>**
>>* FOM (Flow Object model)*
>>**
>
>
>>Context object
>>
Reinhard Pötz wrote:
**
* FOM (Flow Object model)*
**
Context object
--
--parameters--
getInitParameter(name)
If I interpret th
Reinhard, thank you very much for this great summary of the FOM issues
(and for the Wiki)!
Chris
Reinhard Pötz wrote:
This mail should prepare the upcoming vote on the Cocoon flow
implementation.
Some points are pretty clear but some would need some more comments -
especially
- stateful compo
13 matches
Mail list logo
