Stefano Mazzocchi wrote:

void callAction(name,map) -> invoques the action indicated by the given
name and pass the given map as model


How action returns its result? If callAction stays... why not:

map act(name, map)
map match(name, pattern, map)
boolean select(name, pattern, map)


Session getSession()


...

-------- properties ---------

cocoon.request -> the request object
cocoon.response -> the response object
cocoon.log -> the log object


Why session is not a property, as request and response.



---------------------------------------------------------------------------
The Cookie Object
---------------------------------------------------------------------------

This object is a wrapper around the Cookie object provided by the
Environment.

--------- methods -------

getName()
getVersion()
setVersion(version)

values
setValue(value)
getValue()

comment
setComment(purpose)
getComment

domain
setDomain(domain)
getDomain()

age
setMaxAge(age)
getMaxAge()

path
setPath(path)
getPath()

secure
setSecure(secure)
getSecure()

-------- properties ------


Cookie's properties could be made available via properties:


 cookie.name
 cookie.version
...


---------------------------------------------------------------------------
The Request Object
---------------------------------------------------------------------------

-------- properties ---------

[name] -> maps to the parameter indicates with the name

For example

request.blah

is equivalent to

request.getParameter("blah")


Attributes, headers, cookies also could be available via JS array:


 request.cookies['name'] or request.cookies.name
 request.headers['referer'] or request.headers.referer
...


Hope these suggestions make sense.


Vadim




Reply via email to