cocoon.process uri argument (was RE: sendPage, sendPageAndWait uri argument)

[Bruno Dumon <br...@outerthought.org>]

On Mon, 2003-08-04 at 17:41, Unico Hommes wrote:
> On a related note: the cocoon.process(uri,object,outStream) FOM function
> is always resolved as cocoon:// . Do you think this should behave as
> sendPage(AndWait)?

To provide the necessary context for others: this would mean that an uri
starting with a slash is resolved starting from the root sitemap, while
an uri not starting with a slash is resolved against the current
sitemap.

I think that would make a lot of sense, +1 from me. This would break
existing uses of that method though, but I think we better change it now
than later. Anyone else?

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org

Re: cocoon.process uri argument (was RE: sendPage, sendPageAndWait uri argument)

[Geoff Howard <co...@leverageweb.com>]

Bruno Dumon wrote:
> On Mon, 2003-08-04 at 17:41, Unico Hommes wrote:
> 
>>On a related note: the cocoon.process(uri,object,outStream) FOM function
>>is always resolved as cocoon:// . Do you think this should behave as
>>sendPage(AndWait)?
> 
> 
> To provide the necessary context for others: this would mean that an uri
> starting with a slash is resolved starting from the root sitemap, while
> an uri not starting with a slash is resolved against the current
> sitemap.
> 
> I think that would make a lot of sense, +1 from me. This would break
> existing uses of that method though, but I think we better change it now
> than later. Anyone else?
> 

+1 from me.

Geoff

Re: cocoon.process uri argument (was RE: sendPage, sendPageAndWait uri argument)

[Gianugo Rabellino <gi...@apache.org>]

Bruno Dumon wrote:
> On Mon, 2003-08-04 at 17:41, Unico Hommes wrote:
> 
>>On a related note: the cocoon.process(uri,object,outStream) FOM function
>>is always resolved as cocoon:// . Do you think this should behave as
>>sendPage(AndWait)?
> 
> 
> To provide the necessary context for others: this would mean that an uri
> starting with a slash is resolved starting from the root sitemap, while
> an uri not starting with a slash is resolved against the current
> sitemap.

Oh! Thanks, now I get it.

> I think that would make a lot of sense, +1 from me. This would break
> existing uses of that method though, but I think we better change it now
> than later. Anyone else?

+1 here too. I'm more than glad to change my code in exchange for 
coherence and ease of use.

Ciao,

-- 
Gianugo Rabellino
Pro-netics s.r.l. -  http://www.pro-netics.com
Orixo, the XML business alliance - http://www.orixo.com
     (Now blogging at: http://blogs.cocoondev.org/gianugo/)

RE: cocoon.process uri argument (was RE: sendPage, sendPageAndWait uriargument)

[Reinhard Pötz <re...@gmx.net>]

From: Bruno Dumon

> 
> On Mon, 2003-08-04 at 17:41, Unico Hommes wrote:
> > On a related note: the cocoon.process(uri,object,outStream) FOM 
> > function is always resolved as cocoon:// . Do you think this should 
> > behave as sendPage(AndWait)?
> 
> To provide the necessary context for others: this would mean 
> that an uri starting with a slash is resolved starting from 
> the root sitemap, while an uri not starting with a slash is 
> resolved against the current sitemap.
> 
> I think that would make a lot of sense, +1 from me. This 
> would break existing uses of that method though, but I think 
> we better change it now than later. Anyone else?

+1 for me (the person who implements this should make sure that
a note is added to status.xml describing the "new" behaviour of
the uri value in sendPage(AndWait) and process)

Cheers,
Reinhard