Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

fix incorrect example encoding & a typo #6

Merged
merged 1 commit into from

2 participants

Benjamin Atkin Konstantin Haase
Benjamin Atkin

I saw that the array example didn't quite look right, and sure enough, OTNetstring encodes it differently from what is shown in the README. I also found a typo.

Konstantin Haase rkh merged commit d56b068 into from
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on May 18, 2011
  1. Benjamin Atkin
This page is out of date. Refresh to see the latest.
Showing with 2 additions and 2 deletions.
  1. +2 −2 README.md
4 README.md
View
@@ -4,7 +4,7 @@ Similar to [Tagged Netstrings](http://tnetstrings.org/), but optimized for strea
What changed: The type info is not at the end of the encoded data, but at the beginning, right after
the size info. That way nested objects can be created while reading from the stream. Therefore it is
-rather similar to [Bencode](http://en.wikipedia.org/wiki/Bencode), plus the Nestring advantage of
+rather similar to [Bencode](http://en.wikipedia.org/wiki/Bencode), plus the Netstring advantage of
always knowing how many bytes to read.
Objects look like this:
@@ -14,7 +14,7 @@ Objects look like this:
42 2:42# 2#42 i42e
"hi" 2:hi, 2,hi 2:hi
true 4:true! 4!true (not possible)
- [1] 4:1:1#} 3:{1#1 li1ee
+ [1] 4:1:1#} 3[1#1 li1ee
{"a" => "b"} 8:1:a,=1:b,} 6{1,a1,b d1:a1:be
Similar implementations (both pure ruby, using recursion for nested objects) show the performance
Something went wrong with that request. Please try again.