Skip to content
Browse files

Mention @mnot's htracr.

  • Loading branch information...
1 parent 2646b7f commit 0ccd60340287a2c23d80554c592c8a0d86347599 @mranney committed Nov 26, 2010
Showing with 6 additions and 2 deletions.
  1. +6 −2 README.md
View
8 README.md
@@ -8,10 +8,14 @@ It has been tested on OSX and Linux.
`node_pcap` is useful for many things, but it does not yet understand all common protocols. A popular reason
to use this package is `examples/http_trace`, described below.
-## Why?
+Another great reason to use `node_pcap` is
+[htracr](https://github.com/mnot/htracr), written by Mark Nottingham.
+
+## Why capture packets in JavaScript?
There are already many tools for capturing, decoding, and analyzing packets. Many of them are thoroughly
-tested and very fast. Why would anybody want to capture and manipulate packets in JavaScript? A few reasons:
+tested and very fast. Why would anybody want to do such low level things like packet capture and analysis
+in JavaScript? A few reasons:
* JavaScript makes writing event-based programs very natural. Each packet that is captured generates an
event, and as higher level protocols are decoded, they might generate events as well. Writing code to handle

0 comments on commit 0ccd603

Please sign in to comment.
Something went wrong with that request. Please try again.