Hi,
this is my first post here, so greetings everyone and congrats to those commited to the amule development
what are the possibilities of future development of web server support under amule ?
I once discussed this with some ppl on irc.freenode.net:#irc and the general idea that was concluded upon that discussion was that the latency of web pages under p2p was a problem only soluble if ppl accepted to cache mirror pages into their HD
The problem is that people could be in average, reticent to cache a web page after viewing it. Just for reference overnet solves this keeping the cached data encrypted, so the client doesnt know what data he is caching, but the caching priority of files is builded over demand of files (so more demanded files are more widespread). Or at least is how i understand it
In principle one could think that a client that accepted to temporarily cache data according to some criteria (imposed by whom? servers? or file demand?) could be benefited by policies that prioritized those clients of queues, but this can easily be tweaked at the client level by faking the caching feature, unless someone knows how to efficiently verify a encrypted cache is faithful?
Im not expert on these topics, but i was wondering what the developers think of these issues, and what they think in how all these could drive amule (or other p2p clients) to support web and html entirely from p2p networks, without relying on centralized servers, as it is up to this day
cheers!
