Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 43379 invoked from network); 1 Oct 2009 16:06:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Oct 2009 16:06:57 -0000 Received: (qmail 93668 invoked by uid 500); 1 Oct 2009 16:06:53 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 93230 invoked by uid 500); 1 Oct 2009 16:06:53 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 93038 invoked by uid 99); 1 Oct 2009 16:06:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2009 16:06:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kowsik@gmail.com designates 209.85.220.209 as permitted sender) Received: from [209.85.220.209] (HELO mail-fx0-f209.google.com) (209.85.220.209) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2009 16:06:42 +0000 Received: by fxm5 with SMTP id 5so313150fxm.3 for ; Thu, 01 Oct 2009 09:05:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=b2PHOX+jRWKDPop5mDQHc8udeZW1X90Hx9p3WJTb4Vc=; b=Luwgfne4zzeoQcBSez+UnM867D3pENjOaiWyZF0r5BxckJsdpJXkHqddWZuZS3nnff 0feXjwLyKdOpVjF+zdgo1e0To6f0onIVDJ5xkPYjhV8gFlbt9iUdHlwCWy7NlqSAJa2Q no+1dc9cLlgYcbt544POU577QKqLFEfYgcqnM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ZzaSY48lRT7pgVrzkvRJmoaTLONQReP3b6uNpp2R5Wx+C6c/HHkUc+uip9ZEodCv2Y ZoQ+jFNEFJesLUNKTlVzcnES/ToxolUONHU0PxiNE+Z3PfJiAjDE+lZk52vxXW9pm020 NwSi/nYYxOgqRJjtvnvvyKwEicRbIYNUoRnxA= MIME-Version: 1.0 Received: by 10.86.17.4 with SMTP id 4mr1380042fgq.13.1254413121851; Thu, 01 Oct 2009 09:05:21 -0700 (PDT) Date: Thu, 1 Oct 2009 09:05:21 -0700 Message-ID: <7db9abd30910010905m4c536c45u9e6816bcf240a661@mail.gmail.com> Subject: Announcing pcapr Trends From: kowsik To: user@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org With the recent influx of pcaps, the number of protocols and pcaps are getting to the point where interesting trend analysis makes sense. So we set out to find the meaning of it all with multi-dimensional data visualization using Motion Charts (and couchdb). We wanted to find out - How does the coverage and #pcaps for a given protocol trend over time? - When was a protocol first introduced into pcapr? - What is 42 and what does it have to do with packet captures? You can read about this more in our blog http://bit.ly/PhjoT and explore pcapr Trends: http://www.pcapr.net/trends Thanks, The Pcapr Team http://www.pcapr.net/ http://labs.mudynamics.com/ http://twitter.com/pcapr