[MLB-WIRELESS] (Squid Proxy) Paths clearing for wireless networks

[KevinL]

Chances are each cache will only stock a smallish amount of info - we
are, after all, talking about home sites, where each user will have a
fairly good locality of requests, but probably not shared too much with
other houses (except for dynamic content, which can't be cached well
anyway).

There's also an issue that's going to crop up regarding actual setup of
squid or other in a mesh of many proxies (ie. it's hard to do right
without sacrificing lots of speed (waiting for responses from many
servers that are over variable-quality links); and finally there's a
privacy issue (do you want to broadcast the list of url's you're looking
at to all other melbwireless proxy owners?  ;)

Having said all that, it's doable, but it's not going to be something
that reaps great benefit straight away.  I'd suggest the best way is to
setup either a single central, or a small number of regional, squid
"redirectors" - programs that cache info about where content is, and
simply redirect you to the nearest cache that has the info.  Then each
proxy can peer with that/those, rather than building this big "everyone
peers with everyone" mesh.  That also means that privacy can be
addressed on those servers.

Anyway, it's a topic of interest for me - and I can't see why we can't
peer our proxies, one way or another - the trick is going to be in
trying to make it useful, without bogging down people's actual Internet
connections.

KevinL

On Tue, 2002-06-18 at 15:34, Matt Pearce wrote:
> I am curious if someone was to setup a squid cache what sorta size would you
> be talking if you gave Melb Wireless access to it ??
> 
> Matt.
> 
> 
> ----- Original Message -----
> From: "Drew" <drew at wireless.org.au>
> To: <melbwireless at wireless.org.au>
> Sent: Tuesday, June 18, 2002 3:28 PM
> Subject: Re: [MLB-WIRELESS] (Squid Proxy) Paths clearing for wireless
> networks
> 
> 
> > >
> > >
> > >>----------
> > >>8.8 You must not resell, share or otherwise distribute the Service (or
> > >>any portion thereof) to any third party without the prior written
> > >>consent of Optus. For example, you must not provide Internet access to
> > >>others through a dial up or wireless connection, host shell accounts
> > >>over the Internet, provide email or news service or send a news feed.
> > >>----------
> > >>
> > >>
> > >
> > >I guess this one is a matter of interpretation, No we can't allow some
> one
> > >to get the latest kernel via our connection, how ever, if it happens to
> be
> > >that I've downloaded it via the proxy and it's still there and some one
> else
> > >gets it from the proxy, there's nothing wrong with that in /MY/ eyes.
> > >
> > >
> > Right, I never assumed that people could make direct requests, as that
> > would then be sharing the internet connection, but if Squid
> > automatically cached everything that everyone downloaded, and we indexed
> > all this data, we could have a nice little search engine you could check
> > to see if "file X" is on the wlan before you get it off the net.
> > Effectively this shares everyone's connections, but extremely indirectly.
> >
> > D
> >
> >
> >
> > To unsubscribe: send mail to majordomo at wireless.org.au
> > with "unsubscribe melbwireless" in the body of the message
> >
> >
> 
> 
> 
> To unsubscribe: send mail to majordomo at wireless.org.au
> with "unsubscribe melbwireless" in the body of the message
> 



To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message