On 30.Jun.2003 -- 10:29 PM, Sylvain Wallez wrote:
Ricardo Rocha wrote:
Sylvain Wallez wrote:
Ricardo Rocha wrote:
Imo, the flow renders actions (and modules outside the sitemap)
unnecessary, so we shouldn't encourage their continued use by
providing FOM-level support for them. The
Upayavira wrote:
On 30 Jun 2003 at 22:29, Sylvain Wallez wrote:
...
I suggested that components being heavyweight resource, allowing
them to cross continuation boundaries should be prohibited.
Automatic release doesn't seem a good solution to me, as it would
mean that script variables would
Hi Ricardo,
From: Ricardo Rocha [mailto:[EMAIL PROTECTED]
Hi friends,
The following items reflect the discussions Stefano and I have had
around the FOM:
- The load(uri) global function should be supported. This is clearly
needed for nested source file inclusion (which map:script does
Ricardo Rocha wrote:
Hi friends,
The following items reflect the discussions Stefano and I have had
around the FOM:
- The load(uri) global function should be supported. This is clearly
needed for nested source file inclusion (which map:script does not
support).
- The
Reinhard Pötz wrote:
- There should be unrestricted access to all components via
cocoon.getComponent(id).
I'll implement getComponent( id ) and releaseComponent( component) ASAP
because the current flow implementation exposes the component manager
and this leads to a serious bug! If you have
Sylvain Wallez wrote:
Ricardo Rocha wrote:
The following items reflect the discussions Stefano and I have had
around the FOM:
- The load(uri) global function should be supported. This is clearly
needed for nested source file inclusion (which map:script does not
support).
- The
Ricardo Rocha wrote:
Sylvain Wallez wrote:
Ricardo Rocha wrote:
The following items reflect the discussions Stefano and I have had
around the FOM:
- The load(uri) global function should be supported. This is clearly
needed for nested source file inclusion (which map:script does not
On 30 Jun 2003 at 22:29, Sylvain Wallez wrote:
...
I suggested that components being heavyweight resource, allowing
them to cross continuation boundaries should be prohibited.
Automatic release doesn't seem a good solution to me, as it would
mean that script variables would hold released