Git-Mirrors/RetroShare
1
0
Fork 0
mirror of https://github.com/RetroShare/RetroShare.git synced 2024-10-01 02:35:48 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix typo in libresapi documentation

Browse Source
This commit is contained in:
Gio 2016-06-30 22:03:22 +02:00
parent 9f7ef8b46b
commit da4c563223
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
libresapi/src/api/ApiServer.cpp
View File

@ -150,10 +150,10 @@ want generic resource caching mechanism
- dynamic handlers contain result data, and thus get deleted after a while - dynamic handlers contain result data, and thus get deleted after a while
it is even possible to implement a resource-changed check at the highest level it is even possible to implement a resource-changed check at the highest level
this allows to compute everything on the server side and only send chanes to the client this allows to compute everything on the server side and only send changes to the client
the different resource providers don't have to implement a resource changed check then the different resource providers don't have to implement a resource changed check then
a top level change detector will poll them a top level change detector will poll them
of course this does not wokr with a deep resource tree with millions of nodes of course this does not work with a deep resource tree with millions of nodes
for this we have the dynamic handlers, for this we have the dynamic handlers,
they are created on demand and know how to listen for changes which affect them they are created on demand and know how to listen for changes which affect them