Thanks for the feedback, Nick.
> It turned out that my original idea didn't quite work in practice,
> and then I found that webware already includes the feature I needed.
> In http://svn.w4py.org/Webware/trunk/WebKit/Application.py
> Application.__init__ uses a setting called SessionName
> to cont
> Since I want to make a new Webware release soon, I'd like to have that
> fixed there. My idea is to replace the above line by the following:
>
> cookie.setPath(self._transaction.request().adapterName())
>
> This has the advantage that you don't need to configure anything. Can
> you give me feedba
Hi Nick,
you recently posted the following on the Webware mailing list:
> I have two webware apps running on the same domain, one on /default/ and
> the other on /admin/. To avoid the session cookies from colliding, I
> made a small change in HTTPResponse.py:recordSession. The line
> cookie.setPa
Nick Murtagh schrieb:
> Hi,
>
> I have two webware apps running on the same domain, one on /default/ and
> the other on /admin/. To avoid the session cookies from colliding, I
> made a small change in HTTPResponse.py:recordSession. The line
>
> cookie.setPath('/')
>
> is replaced by
>
> cookie.
Hi,
I have two webware apps running on the same domain, one on /default/ and
the other on /admin/. To avoid the session cookies from colliding, I
made a small change in HTTPResponse.py:recordSession. The line
cookie.setPath('/')
is replaced by
cookie.setPath(self._transaction.application().set
