Kees Jongenburger wrote: > > Making a really likeable sollution, (e.g. with Functions or so), would > > require much more thinking and coding to fix such things. > Functions will not fix the problem that a request/response is is sent > info the core (and it won't always work with rmmci)
If for some reason you need the response / request object you have to pass it. For example if you make a function wich produces URL's you have to have the request and response objects. (to get context-path and to encode the URL). I do not know if it a good idea to do such a thing, but anyhow the function framework would make it possible without explicitely having to deal with request and response objects. If you think request and response object should not be valid paramters for functions, I would suggest that you simply don't make such functions. So, the suggested PageContext would still be very 'web-tier oriented' but at least is it not worse then scanpage. A solution based on Function would not be web-tier oriented, at least not in the interfaces. You _could_ make it so, by requesting request and response objects in your function parameters, but well, at least it is up to the implementor of the function then... Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US
