* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #85 (closed design: fixed)

Opened 7 years ago

Last modified 4 years ago

Custom Ranges

Reported by: mnot@pobox.com Owned by: julian.reschke@gmx.de
Priority: normal Milestone: 11
Component: p5-range Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/000c01c7ebe5$4fbdb7a0$ef3926e0$@org

Description

Either flesh out how to define and use custom ranges, or remove them from the spec.

Attachments

i85.diff (2.0 KB) - added by julian.reschke@gmx.de 6 years ago.
Proposed BNF change (for now without allowing "=")

Change History

comment:1 Changed 7 years ago by mnot@pobox.com

  • Component set to auth
  • Milestone set to unassigned

comment:2 Changed 7 years ago by mnot@pobox.com

  • Component changed from auth to range

comment:3 Changed 6 years ago by julian.reschke@gmx.de

  • Owner set to julian.reschke@gmx.de
  • Milestone changed from unassigned to 04

Changed 6 years ago by julian.reschke@gmx.de

Proposed BNF change (for now without allowing "=")

comment:4 Changed 6 years ago by julian.reschke@gmx.de

  • Milestone changed from 04 to unassigned

comment:5 Changed 6 years ago by ylafon@w3.org

There is interest in using new range units, in the W3C's Media Fragments WG, the idea of using 'seconds' as a range unit is discussed to avoid a round-trip for the sole goal of finding an adequate byte range.

A sub-issue is about cache behaviour with some units (like XML subtrees) when a cache wants to merge different fragments.

comment:6 Changed 6 years ago by mnot@pobox.com

  • Milestone changed from unassigned to 06

comment:7 Changed 6 years ago by julian.reschke@gmx.de

From [393]:

Remove bias in favor of byte ranges; allow custom ranges in ABNF. (related to #85)

comment:8 Changed 6 years ago by julian.reschke@gmx.de

From [434]:

adjust whitespace in ABNF; make name of header value production for "Range" consistent with other headers (related to #36 and #85)

comment:9 Changed 6 years ago by julian.reschke@gmx.de

I reviewed the changes in trunk, and I there are two open questions left:

  • what to do with the legacy MS range extension that uses EQ instead of SP
  • whether we need to explain that multipart/byteranges will work for other range units as well

comment:10 Changed 6 years ago by mnot@pobox.com

  • Status changed from new to closed
  • Resolution set to fixed

comment:11 Changed 4 years ago by mnot@pobox.com

  • Priority set to normal
  • Status changed from closed to reopened
  • Resolution fixed deleted
  • Severity set to Active WG Document

p5 isn't clear about how other-range-units should be used or what they mean; if we intend not to establish a registry, we need to give *some* guidance to people about their use.

comment:12 Changed 4 years ago by mnot@pobox.com

  • Milestone changed from 06 to 11

comment:13 Changed 4 years ago by julian.reschke@gmx.de

Plan: actually add the registry.

comment:14 Changed 4 years ago by julian.reschke@gmx.de

From [930]:

add IANA registry for range specifiers (see #85)

comment:15 Changed 4 years ago by julian.reschke@gmx.de

  • Status changed from reopened to closed
  • Resolution set to incorporated

The IANA registry was added in -10. I think we are done with this one.

comment:16 Changed 4 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:17 Changed 4 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.