RE: proposed short-term changes to TCS

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Candidate B in the CfO for Issue-5 refers to a network transaction, and clearly means a single request/response pair or at most a single request + its associated  responses  up to the end of any enclosing tcp connection.

Mike

From: Brad Kulick [mailto:kulick@yahoo-inc.com] 
Sent: 13 November 2013 18:01
To: public-tracking@w3.org (public-tracking@w3.org)
Subject: Fwd: proposed short-term changes to TCS

I believe this is the archived email that Roy was referencing on the call today. I have removed the parts non-relevant to the Network Transaction discussion. 

- -brad

Begin forwarded message:

Resent-From: <public-tracking@w3.org>
From: "Roy T. Fielding" <fielding@gbiv.com>
Subject: proposed short-term changes to TCS
Date: September 20, 2013 4:20:11 PM PDT
To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>

...

 2.3 Network Transaction

  A network interaction is the set of HTTP requests and responses, or any
  other sequence of logically related network traffic caused by a user visit
  to a single web page or similar single action. Page re-loads, navigation,
  and refreshing of content cause a new network interaction to commence.

Section header does not match the defined term.  The defined term does
not make any sense (a network interaction is any message).  The second
sentence needs to be prefixed with "For example, ..."; and "Page re-load"
is a subset of "refreshing of content".

If we want to make requirements on any network interaction, then we
should make them on any sent message, or use "network interaction"
exclusively for single request/response pairs.

If we want to make requirements on a set of network interactions that
result from a single user action, then we should come up with a term
for that (i.e., "user action").

If we want to differentiate between a browser's initial resource
request (initiated by user action) and the sequence of automated
redirects and embedded subrequests that follow as a direct result
of how the browser is instructed or configured to process the results
of those interactions, then we should come up with specific terms
for each of those things.  Note that those interactions are often
caused by configuration outside the referring site's control, such
as how the browser is implemented, what plug-ins have been installed,
what proxies are defined, what accessibility options have been
enabled, and so on; so, we might need to differentiate between
subrequests caused by the user (i.e., "configured requests") and
subrequests caused by content received as the result of an interaction
that instructs the user agent (i.e., "embedded requests"). *phew*

…

Cheers,

Roy T. Fielding                     <http://roy.gbiv.com/>
Senior Principal Scientist, Adobe   <https://www.adobe.com/>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (MingW32)
Comment: Using gpg4o v3.1.107.3564 - http://www.gpg4o.de/
Charset: utf-8

iQEcBAEBAgAGBQJSg8FqAAoJEHMxUy4uXm2JS/gIANWg+rQDMrXTYh4z6+n263o8
POw1Fni950pGl/3eRjCvjal5b9W6L/2YvwW4MeovQa/VKtId2yPccKGG7/Wz4Stc
N22yiwzWUPR64t0neiYbPvyvTmS4WpuLVB5Wzk5r9vq0ODY0x6PKBSQYTVRI7hWr
z79EW6YM1anCpbKMD0bhmjI5lol8QVYeUNWrEG7uRoPWfHfL1SMVwSbEzjTEZRA9
mtx+C2+AMJEKh3dCI2MkrqpHa076cwFfvfODh450CovbP7tL5VaiwoCQrzcwefsD
VTmUPZdULH+Es4Ep1VpB+Cs5eIoqn1MgHI8eQBOFbebwC5qHca1EPagcgv36pdc=
=Ylgj
-----END PGP SIGNATURE-----