Re: Session tracking

To: pitkow@cc.gatech.edu
Subject: Re: Session tracking
From: Jared Rhine <Jared_Rhine@hmc.edu>
Date: Wed, 10 May 1995 00:12:32 -0700
Cc: Multiple recipients of list <www-talk@www10.w3.org>
Message-Id: <199505100712.AAA20303@aslan.math.hmc.edu>
References: <199504212253.SAA18137@hapeville.cc.gatech.edu>
X-Attribution: JRhine
X-Uri: <URL:http://www.hmc.edu/~jared/home>

[Citation date: Fri, 21 Apr 1995 19:31:52 +0500]
JP == James Pitkow <pitkow@cc.gatech.edu>

[The topic was session-tracking proposals, esp the proposed "Session-ID"
header.]

  JP> 1) identify sessions (esp. from firewalled domains)
  JP> [...]
  JP> If the 'From:' field is widely used, you'd have what you wanted(1).

No, I don't believe so, because one of the stated requirements is that we be
able to identify sessions without compromising the identity of the user.

If this is the case, I fail to see how current HTTP practices allow for
session tracking as you claim:

  JP> My point is that the protocol does not need to be changed to handle
  JP> session(1) &/or user identification(2) - WWW browsers/interfaces need
  JP> to pass the right information.

Elaborations?

-- 
Jared_Rhine@hmc.edu / HMC / <URL:http://www.hmc.edu/~jared/home>

"Remember: Once you pull the pin, Mr. Grenade is no longer your friend."
        -- Zippy the Pinhead

Follow-Ups:

Re: Session tracking

From: Franklin Schmidt <frank@localhost.w3.org>

Re: Session tracking

From: pitkow@cc.gatech.edu (James Pitkow)

References:

Re: Session tracking

From: pitkow@cc.gatech.edu (James Pitkow)

Prev: Re: How bout types of colored links?
Next: Expires non-compliance
Index: Message index of www-talk@w3.org mailing list
Thread: Thread index of www-talk@w3.org mailing list