Re: In-kernel Gopher server

[John Bradford]

Quote from Zwane Mwaikambo <zwane@xxxxxxxxxxxxxxxx>:
> On Thu, 23 Oct 2003, John Bradford wrote:
> 
> > Implementing a web-based interface to such data is all very well until
> > you want to access it on a device the size of a wristwatch.
> 
> Wristwatch /proc frobnicating aside, I think your clients are paying for 
> support, perhaps getting yourself to a desk and normal computer might be 
> in their best interests.

Obviously I'm not suggesting it as a normal method of support, it's
just another option.  There might be times when a desk and a normal
computer are more than five minutes away, and having something to
think about on the way there is useful.

> And anyway if you must, what's wrong with a 
> normal pda, ssh and cat(1)?

Nothing, but if we were going to export configuration data at all, it
might as well be done using something more light weight than HTTP and
HTML.

Maybe the wristwatch example was a bit extreme, but what about a
system with very low bandwidth for connectivity?  What if you were
trying to get configuration data back from a spacecraft millions of
miles away?  At 300 BPS or less, and hours of latency, Gopher starts
to look a bit more realistic than getting a shell prompt via ssh :-).

John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/