Return-Path: william@bourbon.usc.edu Delivery-Date: Wed Dec 3 21:40:36 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id mB45eak5024373 for ; Wed, 3 Dec 2008 21:40:36 -0800 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id mB45fTqx019040 for ; Wed, 3 Dec 2008 21:41:29 -0800 Message-Id: <200812040541.mB45fTqx019040@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Example of Ad-hoc network Date: Wed, 03 Dec 2008 21:41:29 -0800 From: Bill Cheng Someone wrote: > Wouldn't the behavior of the OLPC mesh network be a good example > of ad-hoc computing? > > http://wiki.laptop.org/go/Mesh_Network_Details > > When you brought up the subject, the first two things I thought > of were the military sensor networks, and the > One-laptop-per-child initiative. Are you asking about why the lecture slides said that there are no non-military *applications*? I'm not familiar with the OLPC mesh network. Do you know what is the killer app for this network? -- Bill Cheng // bill.cheng@usc.edu