Salut/avahi/meshview issues

[Ricardo Carrano]

Allow me to offer a perspective.

Last year I went to a trial school in Porto Alegre (South part of Brazil).
We grabbed five XOs and went to the housing project where the children live.
There, five kids could use the chat activity from their homes. Everyone was
very excited. The possibilities of the mesh are huge (ok, within limits,
like anything). Let's not forget that no infrastructure is the default
condition around the  world (at least in many years to come).

This is not a waste of our time.

On Jan 30, 2008 2:25 PM, Ivan Krstić <krstic at solarsail.hcs.harvard.edu>
wrote:

> On Jan 30, 2008, at 5:12 PM, Michail Bletsas wrote:
> > For completely serverless environments, what we have is invaluable.
> > The
> > fact that it doesn't scale to large numbers of nodes doesn't make it
> > useless.
>
> I'm similarly confused about people's insistence on a rigid dichotomy
> between the approaches. I never regarded our mesh work to be aimed at
> replacing proper infrastructure -- its goal was to provide a viable
> (if degraded) transport when proper infrastructure was prohibitively
> expensive or otherwise not an option. We always knew that this
> approach carried scaling limits, and that's _fine_. As Michail says,
> this by no means makes the system useless.
>
> > We have serious problems making Avahi and even the Jabber server do
> > their
> > thing with small numbers of nodes
>
> These two are very different. Avahi is hitting design and network
> limits. With Jabber, the problem is our ugly shared roster hack which
> makes the system do something it's not designed to; this is not an
> issue intrinsic to Jabber.
>
> --
> Ivan Krstić <krstic at solarsail.hcs.harvard.edu> | http://radian.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080130/dd0a189b/attachment.html>