Carsten Ziegeler wrote:
Sylvain Wallez wrote:
Great! Why do we need this special wrapper?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 ;-)
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...
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }