summaryrefslogtreecommitdiff
path: root/doc/api.txt
diff options
context:
space:
mode:
authorRyan <ry@tinyclouds.org>2009-09-11 21:04:02 +0200
committerRyan <ry@tinyclouds.org>2009-09-11 21:04:02 +0200
commit5629fd574a01f2d932409b4008593cbf7d77fa74 (patch)
treefc6f7fb138cfeec43f5e4b8ecdfab607cc44d8e5 /doc/api.txt
parentd03c7e38e9dc6f02155617f10daf62e91a35bc35 (diff)
downloadnode-new-5629fd574a01f2d932409b4008593cbf7d77fa74.tar.gz
Add doc note about 'raws' encoding
Diffstat (limited to 'doc/api.txt')
-rw-r--r--doc/api.txt12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/api.txt b/doc/api.txt
index b48344c52a..81595dcd07 100644
--- a/doc/api.txt
+++ b/doc/api.txt
@@ -38,12 +38,12 @@ Server running at http://127.0.0.1:8000/
== API
-Node supports 3 byte-string encodings: ASCII (+"ascii"+), UTF-8 (+"utf8"+),
-and raw binary (+"raw"+). It uses strings to represent ASCII and UTF-8
-encoded data. For the moment, arrays of integers are used to represent raw
-binary data--this representation is rather inefficient. This will
-change in the future, when
-http://code.google.com/p/v8/issues/detail?id=270[V8 supports Blob objects].
+Node supports 4 byte-string encodings. ASCII (+"ascii"+), UTF-8 (+"utf8"+)
+both use the string object, obviously. Then two "raw binary" encodings - one
+uses an array of integers (+"raw"+) and the other uses a string (+"raws"+).
+Neither raw encodings are perfect and thier implemenations are rather
+inefficient. Hopefully the raw encoding situation will improve in the
+future.
Unless otherwise noted, functions are all asynchronous and do not block
execution.