This repository was archived by the owner on Jun 10, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 10, 2021. It is now read-only.
chrome.syncfilesystem #7
Description
I notice in the readme that chrome.filesystem is believed to be a fairly trivial update that is on the dev roadmap.
Will chrome.syncfilesystem be included in this merge/fix? Or is that either (a) additional work or (b) not something that will be possible given what I expect would be a required tie in to chrome.identity?
Reacted by Harper Andrews
Activity
jarrodek commentedon Aug 31, 2016
It won't be possible to make it as Chrome does (seamlessly to the user - except to a part where you need to login to Chrome). There's Drive API for that and Chrome is using this right now for apps. But that's not all because then you have to notified when the file changed and this requires server to receive a notification as described in Push Notifications guide. Since chrome.gcm API won't be easy to implement and taking server cost into the account it makes it probably impossible for service like electron-chrome to implement this feature.
koush commentedon Aug 31, 2016
You don't need Chrome GCM to implement change notifications. Polling would work.
https://developers.google.com/drive/v3/web/manage-changes
Obviously push would be better.
chrome.gcm is implementable easily too, that's part of the web push standard.
https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web?hl=en
Unfortunately, Electron got a bit crashy when i started using service workers. Haven't dug into that further.
My primary use case, Vysor, is using AppEngine push on desktop/web and chrome.gcm in Chrome. The APIs are very similar. It's not possible to polyfill with AppEngine, as the registration tokens will not work with Chrome GCM service's APIs. The web push ones will.
FWIW, I've implemented chrome.identity. I needed to do that to carry over my customer's Chrome store purchases. Same tokens could be used to implement syncFileSystem. I'll be implementing stuff as I need it for my own projects, and though I'm using it for another Chrome app, I won't be getting to that for a while. syncFilesystem is a slick API though. Wouldn't object if that was contributed...