From 351cc5ea0931f460d5f76a84400815377f0fe90f Mon Sep 17 00:00:00 2001
From: Monty <xiphmont@xiph.org>
Date: Mon, 26 Apr 2010 07:26:57 +0000
Subject: Doc tweaks; clarify/make more consistent the Index reasoning.

svn path=/trunk/ogg/; revision=17175
---
 doc/ogg-multiplex.html | 21 +++++++++++----------
 1 file changed, 11 insertions(+), 10 deletions(-)

(limited to 'doc/ogg-multiplex.html')

diff --git a/doc/ogg-multiplex.html b/doc/ogg-multiplex.html
index 41c1481..bd08e25 100644
--- a/doc/ogg-multiplex.html
+++ b/doc/ogg-multiplex.html
@@ -117,16 +117,17 @@ Streams'.</p>
 
 <h3>Seeking</h3> 
 
-<p>Ogg is designed to use a bisection search to implement exact
-positional seeking rather than building an index; an index requires
-two-pass encoding and as such is not acceptable given the requirement
-for full-featured linear encoding.</p>
-
-<p><i>Even making an index optional then requires an
-application to support multiple methods (bisection search for a
-one-pass stream, indexing for a two-pass stream), which adds no
-additional functionality as bisection search delivers the same
-functionality for both stream types.</i></p>
+<p>Ogg is designed to use an interpolated bisection search to
+implement exact positional seeking.  Interpolated bisection search is
+a spec-mandated mechanism.</p>
+
+<p><i>An index may improve objective performance, but it seldom
+improves subjective performance outside of a few high-latency use
+cases and adds no additional functionality as bisection search
+delivers the same functionality for both one- and two-pass stream
+types.  For these reasons, use of indexes is discouraged, except in
+cases where an index provides demonstrable and noticable performance
+improvement.</i></p>
 
 <p>Seek operations are by absolute time; a direct bisection search must
 find the exact time position requested. Information in the Ogg
-- 
cgit v1.2.1