So assuming the site requires "single sign-on". And that there are
several segmentations of the site, each of which could
be handled by a different web-app:
I'm getting the impression that I'm supposed to do some
kind of magic with the session cookie. Is it necessary
to persist all of
Andy Nuss" [EMAIL PROTECTED] wrote:
It seems like each webapp is a separate servlet context, which means
that there is no way to share session info among different components
of the site, if they are segmented as Webapps.
Steve Quail wrote:
Two words:
cookie
database
From my perspective you should have a secure login.
if your login is passed from a non-secure area to a
secure area there's not really that much purpose in
providing the security in the first place. I would
finger that one as good dev tools (trying to stop you
from doing something you
Andrew Oliver wrote:
From my perspective you should have a secure login.
if your login is passed from a non-secure area to a
secure area there's not really that much purpose in
providing the security in the first place.
No argument, but who said anything about logging in? Sessions can be
15, 2000 5:40 PM
To: [EMAIL PROTECTED]
Subject: Re: webapps are useless toys?!
Andrew Oliver wrote:
From my perspective you should have a secure login.
if your login is passed from a non-secure area to a
secure area there's not really that much purpose in
providing the security in the f
Two words:
cookie
database
SteveQ
__ Reply Separator _
Subject: webapps are useless toys?!
Author: "Andy Nuss" [EMAIL PROTECTED] at Internet-po
Date:13/12/00 18:19
Hi,
Does anyone with a need for
I think the idea is that Webapps are distinct self-contained applications
and therefore should not depend on _anything_ outside of the webapp. If you
have components which need to share session info, they _should_ be in the
same webapp. You would then build your webapp as you would any
