The buffer_policy attribute of WATCH is gone. Bring an example up to date.

1 files changed, 10 insertions, 8 deletions

diff --git a/www/protocol-evolution.txt b/www/protocol-evolution.txt
index 44b3a979..6535db79 100644
--- a/www/protocol-evolution.txt
+++ b/www/protocol-evolution.txt
@@ -1,6 +1,6 @@
 = GPSD-NG: A Case Study in Application Protocol Evolution =
 Eric S. Raymond <esr@thyrsus.com>
-v1.2, August 2009
+v1.3, August 2009
 
 == Introduction ==
 
@@ -301,10 +301,11 @@ in memory utilization.
 gpsd hasn't had a requirement to parse JSON yet, just emit it as
 responses?"  Because I fully expected gpsd to have to parse structured
 JSON arguments for commands.  Here's an example, which I'll explain fully
-later but right now just hint at the GPSD-NG equivalent of a 'W+R+J+' command.
+later but right now just hint at the (approximate) GPSD-NG equivalent 
+of a 'W+R+' command.
 
 -------------------------------------------------------------------------
-?WATCH={"raw":1,"buffer_policy":1}
+?WATCH={"raw":1,nmea:true}
 -------------------------------------------------------------------------
 
 Even had I not anticipated parsing JSON arguments in gpsd, I try to
@@ -353,17 +354,18 @@ to write a configuration command that suppresses device display.
 Now we come back to our previous example:
 
 -------------------------------------------------------------------------
-?WATCH={"raw":true,"buffer_policy":1"}
+?WATCH={"raw":true,nmea:true}
 -------------------------------------------------------------------------
 
 This says: "Stream all reports from all devices at me, setting raw
-mode and buffering policy 1." The way to add more controls to this is
-obvious, which is sort of the point - nothing like this could have fit
-in the fixed-length syntax of the old pre-JSON protocol.
+mode and dumping as pseudo-NMEA if it's a binary protocol." The way to
+add more controls to this is obvious, which is sort of the point --
+nothing like this could have fit in the fixed-length syntax of the old
+pre-JSON protocol.
 
 This is not mere theory. At the time of writing, the ?WATCH command is
 fully implemented in gpsd's Subversion repository, and I expect it to
-ship ready for use in our next release (2.40).  Total time to build
+ship ready for use in our next release (2.90).  Total time to build
 and test the JSON parsing infrastructure, the GPSD-NG parser, and the
 gpsd internals enhancements needed to support multi-device listening?
 About a working week.