There would be a password request for each index view or control feature - perhaps something like the apache .htaccess files ?
So that we can define an individual access range. A user normally would not be able to purge anything from the main-index directly, but pehaps she can do with her 'own' stuff through her lasttime index.
It would not neccessarily be waterproof safe or secure, but rather a kind of insurance against mistakes from unexperienced users.
Underlying my assumption that getting wwwoffle to this kind of users, by integrating with the whole internet desktop functionality,
could be a fruitful developement goal. At least, as long as browsers don't provide a full cache administration and features like ordering, recursive fetching,
different indices and cache searching themselves. I'm yet not sure what's the state of art (mac, sun, novell ?).
There could be internal bridges between wwwoffle and the browsers' history, bookmark database, page context menu, appearence (modify html) settings,... perhaps to the extend of a seperate 'proxycontrol' panel with buttons for the main functions.
By integrating i mean the browser's still the UI , and the proxy daemon still a daemon, but why not create a seperate a middle layer.
A daemon's API, sth. the browser talks to. The API calls would be the same for all types of machines or browsers.
Implementation of its features would probably be a task for the browsers developer team.
This is just a little philosophy, of course. (And perhaps should go to a seperate thread.)
Anyway, i think Andrew generally is interested in how we like to work with his cool stuff ...
so.
Andrew M. Bishop wrote:
other though. What has been described will lead to a shared cache so that an index will show the pages that have been requested by other people. All of the WWWOFFLE processes will need to run as the same user (or at least have write permission to the shared cache). This means that you have to stop people purging each others files etc. If the users cannot be trusted then the original idea with one master WWWOFFLE server and the others as clients of it is probably the safest.
