> > For example, the indexer could run as a simple HTTP proxy.
> > You configure your browser to use this local proxy (which
> > could, in turn, forward requests to a squid or other proxy).
>> couldn't this be a user-space proxy !
> Every user runs their own copy of it from their .bashrc and it
> stores the history in a file in their homedir or whatever.
> The only question I have is how easy would it be for the proxy
> to be certain what user/process a request came from - to
> stop others decided to fill your index with junk.
That's exactly the problem I came up against. Also, since the
search engine that uses the resulting index should really be
accessible via HTTP, it needs to be able to tell what user
sent the search request. Otherwise I can just do a 'search
for URL=*' on your indexer and get all the URLs you've visited.
> Can a user-space prog wait on any port (over 1024)? and thus
> be a proxy so none of the admins would need to help implement this
Yes. That's exactly what I had in mind.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!