class SyncFileItem;
typedef QSharedPointer<SyncFileItem> SyncFileItemPtr;
+/** Collection of parameters for initializing a Vfs instance. */
struct OCSYNC_EXPORT VfsSetupParams
{
+ /// The full path to the folder on the local filesystem
QString filesystemPath;
+ /// The path to the synced folder on the account
QString remotePath;
+ /// Account url, credentials etc for network calls
AccountPtr account;
- // The journal must live at least until the stop() call
+
+ /** Access to the sync folder's database.
+ *
+ * Note: The journal must live at least until the Vfs::stop() call.
+ */
SyncJournalDb *journal;
+ /// Strings potentially passed on to the platform
QString providerName;
QString providerVersion;
};
+/** Interface describing how to deal with virtual/placeholder files.
+ *
+ * There are different ways of representing files locally that will only
+ * be filled with data (hydrated) on demand. One such way would be suffixed
+ * files, others could be FUSE based or use Windows CfAPI.
+ *
+ * This interface intends to decouple the sync algorithm and Folder from
+ * the details of how a particular VFS solution works.
+ *
+ * An instance is usually created through a plugin via the createVfsFromPlugin()
+ * function.
+ */
class OCSYNC_EXPORT Vfs : public QObject
{
Q_OBJECT
public:
+ /** The kind of VFS in use (or no-VFS)
+ *
+ * Currently plugins and modes are one-to-one but that's not required.
+ */
enum Mode
{
Off,
virtual Mode mode() const = 0;
- // For WithSuffix modes: what's the suffix (including the dot)?
+ /// For WithSuffix modes: what's the suffix (including the dot)?
virtual QString fileSuffix() const = 0;
+
+ /// Must be called at least once before start(). May make sense to merge with start().
virtual void registerFolder(const VfsSetupParams ¶ms) = 0;
+
+ /** Initializes interaction with the VFS provider.
+ *
+ * For example, the VFS provider might monitor files to be able to start a file
+ * hydration (download of a file's remote contents) when the user wants to open
+ * it.
+ */
virtual void start(const VfsSetupParams ¶ms) = 0;
+
+ /// Stop interaction with VFS provider. Like when the client application quits.
virtual void stop() = 0;
+
+ /// Deregister the folder with the sync provider, like when a folder is removed.
virtual void unregisterFolder() = 0;
+
+ /** Return true when download of a file's data is currently ongoing.
+ *
+ * See also the beginHydrating() and doneHydrating() signals.
+ */
virtual bool isHydrating() const = 0;
- // Update placeholder metadata during discovery
+ /** Update placeholder metadata during discovery.
+ *
+ * If the remote metadata changes, the local placeholder's metadata should possibly
+ * change as well.
+ *
+ * Returning false and setting error indicates an error.
+ */
virtual bool updateMetadata(const QString &filePath, time_t modtime, quint64 size, const QByteArray &fileId, QString *error) = 0;
- // Create and convert placeholders in PropagateDownload
+ /// Create a new dehydrated placeholder. Called from PropagateDownload.
virtual void createPlaceholder(const QString &syncFolder, const SyncFileItemPtr &item) = 0;
+
+ /** Convert a new file to a hydrated placeholder.
+ *
+ * Some VFS integrations expect that every file, including those that have all
+ * the remote data, are "placeholders". This function is called by PropagateDownload
+ * to convert newly downloaded, fully hydrated files into placeholders.
+ */
virtual void convertToPlaceholder(const QString &filename, const SyncFileItemPtr &item) = 0;
- // Determine whether something is a placeholder
+ /// Determine whether the file at the given absolute path is a dehydrated placeholder.
virtual bool isDehydratedPlaceholder(const QString &filePath) = 0;
- // Determine whether something is a placeholder in discovery
- // stat has at least 'path' filled
- // the stat_data argument has platform specific data
- // returning true means that the file_stat->type was set and should be fixed
+ /** Similar to isDehydratedPlaceholder() but used from sync discovery.
+ *
+ * This function shall set stat->type if appropriate.
+ * It may rely on stat->path and stat_data (platform specific data).
+ *
+ * Returning true means that type was fully determined.
+ */
virtual bool statTypeVirtualFile(csync_file_stat_t *stat, void *stat_data) = 0;
signals:
+ /// Emitted when a user-initiated hydration starts
void beginHydrating();
+ /// Emitted when the hydration ends
void doneHydrating();
};
+/// Check whether the plugin for the mode is available.
OCSYNC_EXPORT bool isVfsPluginAvailable(Vfs::Mode mode);
+
+/// Return the best available VFS mode.
OCSYNC_EXPORT Vfs::Mode bestAvailableVfsMode();
+
+/// Create a VFS instance for the mode, returns nullptr on failure.
OCSYNC_EXPORT Vfs *createVfsFromPlugin(Vfs::Mode mode, QObject *parent);
} // namespace OCC