cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Kossakowski <>
Subject Re: More problems with implementing servlet services
Date Wed, 09 May 2007 13:33:22 GMT
Reinhard Poetz pisze:
> Grzegorz Kossakowski wrote:
>> Actually, HTTP protocol is always used in service calls but components 
>> just hide low-level details of HTTP and integrate calls with 
>> pipelining model. In current (and basic) state of implementation one 
>> could call services remotely because all data is carried using 
>> standard HTTP methods like headers and POST request method with data 
>> encoded in request body.
>> I hardly see how this could be achieved with whole environment, the 
>> only option would be to serialize it to the byte stream and send it as 
>> POST too. However, I guess that even if it was technically possible it 
>> would be very impractical.
>> It's important to realize that you still can pass portion of 
>> environment data that service really needs using for example posted 
>> XML or http headers/parameters. For small, focused services 
>> implemented by simple servlets usually it will be enough.
> This fallback mechanism is what I was asking for and good enough.
>> Problem arises only when you make a call from Cocoon's sitemap servlet 
>> to another Cocoon's sitemap servlet that can make use of all goodies 
>> we have, especially, flowscript.
>> I feel that passing whole env. via request object not using HTTP 
>> methods is kind of hack but I have no other idea and I guess only 
>> Cocoon servlets are those who are going to make a use of whole env, 
>> anyway.
> As long as the fallback mechanism as described by you above works, I 
> don't see a problem with your solution.

I'm little puzzled with your resposne, I was talking about fallback mechanism only for passing
SAX events.

What other fallback mechanism you referred to? Did you mean a possiblity to pass some portion
of env.?

Grzegorz Kossakowski

View raw message