Hi Grzegorz,
do we need all information from the environment? If not, we could add
custom X-Cocoon-* Headers that can also be exchanged in more
decoupled scenarios where servlet services are actual remote websites.
Lars
Am 08.05.2007 um 18:29 schrieb Grzegorz Kossakowski:
Another problem is that if we want servlet services really usable
we need to forward Environment to the called service. An obvious
example is service that takes effort of styling Forms and handling
Ajax requests. It needs to access all environment data to get run
Forms machinery properly. I was thinking about it for a while and I
have no appealing idea how to solve it. I guess that this task is
far beyond HTTP capabilities and in this area we need to break
conformity with HTTP specification. I mean that we just attach
Environment object to the BlockCallHttpServletRequest instance and
we'll modify cocoon's core a little bit to detect that request is
service call so it will be able to make us of forwarded Environment.
--
Lars Trieloff
visit http://www.mindquarry.com/
