SAXESS - Hussayn Dabbous wrote:
I agree that the ideal situation is the ability to forward cookies between the remote application and the real client (i.e. a browser requesting from Cocoon) and vice versa. Additionally, those cookies should be readable *and* modifyable by logic inside Cocoon.Maybe HTTPClient supports proxy functionalities? That may help getting things done...
If you are interested, we can get into a discussion. Maybe we should wait until our preliminary results are available?
Unfortunatelly I just started with HttpClient and haven't found any related functionality in the documentation. I posted a question on commons-users (see [1]).
Let's wait a bit and see what happens :-)
[1] http://marc.theaimsgroup.com/?l=jakarta-commons-user&m=104038254206245&w=2
Manos
regards, hussaynEmmanuil Batsis (Manos) wrote:
I'm in a similar situation (but without cocoon) and investigating the HttpClient [1](from commons). HttpClient can hadle cookies which makes it a session-able HTTP client.
My question here is, does it make sense to try and build a generator for Cocoon with the above? I am under the impression that sitemap logic is not session-aware (as a client of remote applications).
[1] http://jakarta.apache.org/commons/httpclient/
Thanks,
Manos
SAXESS - Hussayn Dabbous wrote:
I am talking about following setup: You have two separate webapplications not necessaryly running in the same container! One app is the cocoon application. The other app is a session based webapp. Now you setup a pipeline, which gathers data from the other webapp. Here you are lost. What basically is missing: The session state is usually preserved within cookies, or by URL-rewriting. If sessions are cookie based, we need to pass the session cookie through cocoon. And this is definitely not implemented yet. Or my understanding of the cocoon code is absolutley wrong ;-)--------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>--------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
--------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
