You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by "Emmanuil Batsis (Manos)" <mb...@humanmarkup.org> on 2002/12/20 11:18:15 UTC

[Question] Re: cocoon-session management.

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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


RE: [Question] Re: cocoon-session management.

Posted by Conal Tuohy <co...@paradise.net.nz>.
See the WebServiceProxyGenerator:
http://outerthought.net/wiki/Wiki.jsp?page=WebServiceProxyGenerator

> -----Original Message-----
> From: Emmanuil Batsis (Manos) [mailto:mbatsis@humanmarkup.org]
> Sent: Saturday, 21 December 2002 00:24
> To: cocoon-users@xml.apache.org
> Subject: Re: [Question] Re: cocoon-session management.
>
>
>
>
> SAXESS - Hussayn Dabbous wrote:
> > Maybe HTTPClient supports proxy functionalities?
> > That may help getting things done...
>
> 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.
>
>
> > 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
>


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: [Question] Re: cocoon-session management.

Posted by "Emmanuil Batsis (Manos)" <mb...@humanmarkup.org>.

SAXESS - Hussayn Dabbous wrote:
> Maybe HTTPClient supports proxy functionalities?
> That may help getting things done...

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.


> 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, hussayn
> 
> Emmanuil 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:     <co...@xml.apache.org>
>> For additional commands, e-mail:   <co...@xml.apache.org>
>>
> 
> 
> ---------------------------------------------------------------------
> 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:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>
> 
> 
> 
> 


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: [Question] Re: cocoon-session management.

Posted by SAXESS - Hussayn Dabbous <da...@saxess.com>.
Yes, in principle you are right. You could use
HTTPClient to organise the session management.

But you will have to consider other points:

1.) Your subsession may be authenticated. Thus you
will have to maintain interactions between the
cocoon-client and the far-application server to
get logged into your subsystem. Then you would
be faced with flow control iussues...
This may be a problem, since your cocoon-client
operates silently in the background...

2.) Besides this, your subsession might want to
pass permanent cookies to it's client. This may
be possible with HTTP-Client, but then you will
have to maintain a cookie-database for your
cocoon clients... (No problem if your app runs
only for yourself ;-)

Both points are from my point of view problematic.
In certain cases the approach work. In other cases
you might run into complexity problems.

I would rather keep the interaction at the browser
site, thus it is the browser who keeps the cookies
and it is the cocoon-client, who acts as a proxy and
passes the cookies to the underlying subsystem...
OK, here you face other problems, but these problems
can at least be solved in general without getting
too mutch complexity into the game...
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?

regards, hussayn

Emmanuil 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:     <co...@xml.apache.org>
> For additional commands, e-mail:   <co...@xml.apache.org>
> 


---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>