cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <agalla...@agssa.net>
Subject Re: [VOTE] Unrestricting the FOM
Date Wed, 09 Feb 2005 18:13:45 GMT
On Mie, 9 de Febrero de 2005, 12:06, Sylvain Wallez dijo:
> Carsten Ziegeler wrote:
>
>> Sylvain Wallez wrote:
>>
>>> Hi team,
>>>
>>> Several months later, it's done (the vote started on 14-06-2004).
>>>
>>> cocoon.request, cocoon.response, cocoon.context and cocoon.session
>>> are now unrestricted.
>>>
>>> The only difference with the real objects is that a special wrapper
>>> is used for request, response and context that shows their respective
>>> attributes are JS properties (not sure I personally like it, but
>>> that's how they have been since the beginning).
>>>
>>> This closes a lot of open bugs ;-)
>>>
>> Great! Why do we need this special wrapper?
>
>
> Because removing it means a backwards incompatible change!
>
> It adds small syntactic sugar by allowing you to write
> 'cocoon.session.blah' instead of 'cocoon.session.getAttribute("blah")'
> and the same on request and context.
>
> I personally didn't knew about it until today and therefore never used
> it...

I thought in the form flow samples is. The construction is often used to
test request params. ;-)

ie: cocoon.request.myButton

Best Regards,

Antonio Gallardo


Mime
View raw message