[Prev][Next][Index][Thread]
cc:Mail UUCPLINK 2.0 Undeliverable Message
User mutual!OCARROLL at TMC_HH@mutual.co.uk is not defined
Original text follows
-----------------------------------------
Received: by ccmail
Received: from uupsi by co.uk (UUPC/extended 1.11) with UUCP;
Wed, 18 Sep 1996 01:57:00 BST
Received: from www19.w3.org by sys4.cambridge.uk.psi.net (8.7.5/SMI-5.5-UKPSINet)
id BAA13649; Wed, 18 Sep 1996 01:47:18 +0100 (BST)
Received: by www19.w3.org (8.6.12/8.6.12) id UAA28853; Tue, 17 Sep 1996 20:45:32 -0400
Resent-Date: Tue, 17 Sep 1996 20:45:32 -0400
Resent-Message-Id: <199609180045.UAA28853@www19.w3.org>
From: "Phoebe Couch" <Phoebe.Couch@library.ucsf.edu>
X-ccAdmin: mutual@uupsi
Message-Id: <9609171756.ZM966@altitude.ckm.ucsf.edu>
Date: Tue, 17 Sep 1996 17:56:57 -0700
In-Reply-To: otisg@panther.middlebury.edu (Otis Gospodnetic)
"Re: question :)" (Sep 17, 8:22pm)
References: <9609180022.AA121721@panther.middlebury.edu>
X-Mailer: Z-Mail (3.2.2 10apr95 MediaMail)
To: otisg@panther.middlebury.edu (Otis Gospodnetic)
Subject: Re: question :)
Cc: www-rdb@w3.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-List-URL: http://www.w3.org/pub/WWW/Archives/Public/www-rdb/
Resent-From: www-rdb@w3.org
X-ccAdmin: mutual@uupsi
X-Mailing-List: <www-rdb@w3.org> archive/latest/285
X-Loop: www-rdb@w3.org
Sender: www-rdb-request@w3.org
Resent-Sender: www-rdb-request@w3.org
Precedence: list
From: Otis Gospodnetic <otisg@panther.middlebury.edu>
>We would need something that would allow users to login to their entries in
>the database, change the info in those entries, and logout.
I am afraid that you are running into a stateful operation(login) in
a stateless environment (http) situation.
I fake it for one of my applications using timestamps, but it is for a limited
audience only, so it will not work for you.
The state of a user being logged in will have to be maintained somewhere,
either in a session or some other means. I think naviserver will hold the
connection open and maybe will allow you to have a session. A regular
http server will not do that for you. We have a session server for one of
our apps,(it speaks http, but keeps states) but it is a lot of work to
develop one. I am not aware of any standard way to do sessions right now,
cookies may be the way to go. You also have to worry
about timeouts, since users may not logout. If you can by-pass the web browser
and connect directly to the database with an X client or Java, maybe it will
be easier. I am rambling now...
Let me know what you find out, as things like this is part of my daily
existence.
P.
--
Software Engineer mail: phoebe@ckm.ucsf.edu
UCSF Library & Ctr for Knowledge Mgt phone: 415/476-3577
530 Parnassus Avenue, Box 0840 fax: 415/476-4653
San Francisco, California 94143