Spec update: In V2, incremental Snappy is the new Snappy

In other words, non-incremental Snappy compression is no longer valid Sereal in protocol version 2.
Sereal · Jun 25, 2013 · b67440d · b67440d
1 parent 996260b
commit b67440d
Showing 1 changed file with 8 additions and 4 deletions.
diff --git a/sereal_spec.pod b/sereal_spec.pod
@@ -75,14 +75,18 @@ Raw Sereal format. The data can be processed verbatim.
 
 =item 1
 
-Compressed Sereal format, using Google's Snappy compression internally.
+B<This is not a valid document type for Sereal protocol version 2!>
-Prefer I<2> wherever possible.
+
+In Sereal protocol version 1, this used to be
+"Compressed Sereal format, using Google's Snappy compression internally."
+It has long been advised to prefer I<2>, "incremental-decoding-enabled
+compressed Sereal," wherever possible.
 
 =item 2
 
 Compressed Sereal format, using Google's Snappy compression internally as
-format I<1>, but supporting incremental-parsing. Preferred over I<1> as this
+format I<1>, but supporting incremental-parsing. Long preferred over
-is considered a bug fix in the Snappy compression support.
+I<1> as this is considered a bug fix in the Snappy compression support.
 
 The format is: