I'd like to start an experiment to create a serverless DHT containing a user's library of game metadata, so that users can opt to share their library's metadata with the DHT as a preferred option to fetching from TheGamesDB. Update calls would still occur, but the idea is that users' libraries would constitute a partial distributed mirror of TheGamesDB, thereby significantly reducing the load on your servers, should this daemon become widely used.
The DHT client would be a daemon with few responsibilities:
* Monitor the user's library for changes.
* Respond to peer requests for data
* Request updates and data from peers
* Periodically request updates (/Games/Updates) from TheGamesDB if none available from peers; these would be throttled to one request per minute. (Aside: is it possible to filter the update call on a per-game or per-games basis?)
* Failing DHT data, fall back to searching TheGamesDB for the game in question.
I'm aware that keys are on hold pending some new-API refinement. Gimme a yell when you've cleared your hurdles and can respond to API key requests.
Key request for DHT mirroring experiment
Forum rules
API Keys (unique userpage)
Usergroups (request API Users access here after posting a new topic below)
Please provide a basic overview of your proposed use of the API.
Any request lacking this information will be denied pending an appropriate response.
Please do not request keys as end users of another project, as those projects should request and properly implement their own keys. Key requests of this nature will be removed in the interest of more efficiently handling project requests. Assistance may be available upon contact for projects experiencing issues utilizing the current API.
API Keys (unique userpage)
Usergroups (request API Users access here after posting a new topic below)
Please provide a basic overview of your proposed use of the API.
Any request lacking this information will be denied pending an appropriate response.
Please do not request keys as end users of another project, as those projects should request and properly implement their own keys. Key requests of this nature will be removed in the interest of more efficiently handling project requests. Assistance may be available upon contact for projects experiencing issues utilizing the current API.
Re: Key request for DHT mirroring experiment
Hi there,
sounds like an interesting idea, I'm not entire familiar with the working of DHT, but I assume it support a form of updates to allow an updated DB?
You've been granted an API key which you can access through this page.
if you ever go public with your project, please post in this thread notifying us of that.
please check the Announcement forum on regular bases to ensure compliance with any changes or updates.
Regards
Zer0xFF
sounds like an interesting idea, I'm not entire familiar with the working of DHT, but I assume it support a form of updates to allow an updated DB?
You've been granted an API key which you can access through this page.
if you ever go public with your project, please post in this thread notifying us of that.
please check the Announcement forum on regular bases to ensure compliance with any changes or updates.
Regards
Zer0xFF
Regards
Zer0xFF
Zer0xFF