4 ms·
Interesting concept but my concern would be the frequency of synchronization. Would the service check remote documents (potentially several megs in size) every
by ktavera 14y ago
Interesting concept but my concern would be the frequency of synchronization. Would the service check remote documents (potentially several megs in size) every minute to see if they have changed? every 5 minutes? every 30 seconds? Unless there was some kind of pseudo-dropbox component running on the server where the documents are hosted to alert the service that there is a new version of a document, this doesn't seem viable. I could be wrong though, what approach were you thinking for this?
- mad44 14y agoWhy not pick daily as the frequency to check (application does not necessitate tight-synchronization anyway). We can have on-demand based synchronization as a backup/safety net plan. If a user actually opens the local document, the client-portion of the service will call the server-portion of the service (which hosts the documents) and that in turn will check if there is a change in the original/remote document. If the document is a popular document, it will stay up-to-date with much finer granularity than a day.
- mad44 14y agoThis idea may as well be seen as extending CDNs to reach out and embrace the pc/laptops as the last hop. The client-component of this service may interact with CDNs, maybe.