OX Drive API - Revision history

Tobias.friedrich at 05:31, 20 October 2017

2017-10-20T05:31:13Z

← Older revision		Revision as of 05:31, 20 October 2017
Line 2,229:		Line 2,229:

	Example:		Example:
	==> PUT http://192.168.32.191/ajax/drive?action=~~updateFolder~~&session=35d55f0bd2284e78a8eb4dba99b1310b&root=9542&path=/test&checksum=d41d8cd98f00b204e9800998ecf8427e		==> PUT http://192.168.32.191/ajax/drive?action=updateFile&session=35d55f0bd2284e78a8eb4dba99b1310b&root=9542&path=/test&checksum=d41d8cd98f00b204e9800998ecf8427e
	> Content:		> Content:
	{		{

Tobias.friedrich at 06:58, 5 May 2017

2017-05-05T06:58:37Z

← Older revision		Revision as of 06:58, 5 May 2017
Line 2,171:		Line 2,171:
	* <code>path</code> - The path to the directory to update, relative to the root folder.		* <code>path</code> - The path to the directory to update, relative to the root folder.
	* <code>checksum</code> - The checksum of the directory to update.		* <code>checksum</code> - The checksum of the directory to update.
	* <code>cascadePermissions/code> (optional, available since API version 7) - If set to <code>true</code>, permission changes are also applied to all subfolders recursively.		* <code>cascadePermissions</code> (optional, available since API version 7) - If set to <code>true</code>, permission changes are also applied to all subfolders recursively.

	Request body:<br />		Request body:<br />

Tobias.friedrich at 06:58, 5 May 2017

2017-05-05T06:58:10Z

← Older revision		Revision as of 06:58, 5 May 2017
Line 2,171:		Line 2,171:
	* <code>path</code> - The path to the directory to update, relative to the root folder.		* <code>path</code> - The path to the directory to update, relative to the root folder.
	* <code>checksum</code> - The checksum of the directory to update.		* <code>checksum</code> - The checksum of the directory to update.
			* <code>cascadePermissions/code> (optional, available since API version 7) - If set to <code>true</code>, permission changes are also applied to all subfolders recursively.

	Request body:<br />		Request body:<br />

Tobias.friedrich at 10:20, 10 October 2016

2016-10-10T10:20:36Z

← Older revision		Revision as of 10:20, 10 October 2016
Line 2,415:		Line 2,415:
	}		}

			== Move/Rename a Directory ==

			Available since API version 6. <br />

			Explicitly performs a move or rename operation for a directory. This method is intended for the situation when no phsyical copy of the synchronized data is available on the client.

			GET <code>/ajax/drive?action=moveFolder</code>

			Parameters:
			* <code>session</code> - A session ID previously obtained from the login module.
			* <code>root</code> - The ID of the referenced root folder on the server.
			* <code>path</code> - The path to the directory to update, relative to the root folder.
			* <code>checksum</code> - The checksum of the directory to update.
			* <code>newPath</code> - The new target path to apply, relative to the root folder.

			Response:<br />
			An empty JSON object in case of a successful move. The client should perform the move operation locally afterwards, then enter a normal synchronization cycle to acknowledge any changes.

			Example:
			==> GET http://local.ox/ajax/drive?action=moveFolder&root=163114&apiVersion=6&path=%2ftest&checksum=57ff72d92073bac92f13791bf4e7baf4&newPath=%2ftest3&session=9eabd980fead41d4ac81d32f6c86da5b

			<== HTTP 200 OK (90.064 ms elapsed, 11 bytes received)
			< Content:
			{
			"data": {}
			}

			== Move/Rename a File ==

			Available since API version 6. <br />

			Explicitly performs a move or rename operation for a file. This method is intended for the situation when no phsyical copy of the synchronized data is available on the client.

			GET <code>/ajax/drive?action=moveFile</code>

			Parameters:
			* <code>session</code> - A session ID previously obtained from the login module.
			* <code>root</code> - The ID of the referenced root folder on the server.
			* <code>path</code> - The path to the synchronized folder, relative to the root folder.
			* <code>name</code> - The name of the file version to update.
			* <code>checksum</code> - The checksum of the file version to update.
			* <code>newName</code> - The target name to apply.
			* <code>newPath</code> - The new target path to apply, relative to the root folder.

			Response:<br />
			An empty JSON object in case of a successful move. The client should perform the move operation locally afterwards, then enter a normal synchronization cycle to acknowledge any changes.

			Example:
			==> GET http://local.ox/ajax/drive?action=moveFile&root=163162&apiVersion=6&path=%2f&name=wurst.txt&checksum=f04e78d909d69a8463afd9e4dd159dcc&newName=wurst2.txt&session=213306bec07644ae9b6cc6a16d2be022

			<== HTTP 200 OK (43.6119 ms elapsed, 11 bytes received)
			< Content:
			{
			"data": {}
			}

	= File- and Directory Name Restrictions =		= File- and Directory Name Restrictions =

Tobias.friedrich at 13:43, 15 July 2016

2016-07-15T13:43:06Z

Show changes

Martin.schneider: Move to https://documentation.open-xchange.com/

2016-06-30T08:02:10Z

Move to https://documentation.open-xchange.com/

← Older revision		Revision as of 08:02, 30 June 2016
Line 28:		Line 28:
	= API =		= API =

	As part of the [~~[HTTP_API\|~~HTTP API]], the basic conventions for exchanging messages described there are also valid for this case, especially the [~~[HTTP_API#Low_level_protocol\|~~low level protocol]] and [~~[HTTP_API#Error_handling\|~~error handling]]. Each request against the Drive API assumes a valid server session that is uniquely identified by the session id and the corresponding cookies and are sent with each request. A new session can be created via the [~~[HTTP_API#Module_~~.~~22login~~.~~22\|~~login module]].		As part of the [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API], the basic conventions for exchanging messages described there are also valid for this case, especially the [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (low level protocol)] and [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (error handling)]. Each request against the Drive API assumes a valid server session that is uniquely identified by the session id and the corresponding cookies and are sent with each request. A new session can be created via the [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (login module)].

	The root folder plays another important role for the message exchange. The root folder has a unique identifier. It is the parent server folder for the synchronization. All path details for directories and files are relative to this folder. This folder's id is sent with each request. To select the root folder during initial client configuration, the client may get a list of synchronizable folders with the [[#Get_synchronizable_Folders\|<code>subfolders</code>]] action.		The root folder plays another important role for the message exchange. The root folder has a unique identifier. It is the parent server folder for the synchronization. All path details for directories and files are relative to this folder. This folder's id is sent with each request. To select the root folder during initial client configuration, the client may get a list of synchronizable folders with the [[#Get_synchronizable_Folders\|<code>subfolders</code>]] action.
Line 294:		Line 294:

	=== <code>error</code> ===		=== <code>error</code> ===
	With the <code>error</code> action, file- or directory versions causing a synchronization problem can be identified. The root cause of the error is encoded in the <code>error</code> parameter as described at the [~~[HTTP_API#Error_handling\|~~HTTP API]].		With the <code>error</code> action, file- or directory versions causing a synchronization problem can be identified. The root cause of the error is encoded in the <code>error</code> parameter as described at the [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (error handling)].

	Basically, there are two scenarios where either the errorneous version affects the synchronization state or not. For example, a file that was deleted at the client without sufficient permissions on the server can just be downloaded again by the client, and afterwards, client and server are in-sync again. On the other hand, e.g. when creating a new file at the client and this file can't be uploaded to the server due to missing permissions, the client is out of sync as long as the file is present. Therefore, the boolean parameter <code>quarantine</code> instructs the client whether the file or directory version must be excluded from the synchronization or not. If it is set to <code>true</code>, the client should exclude the version from the <code>clientVersions</code> array, and indicate the issue to the enduser. However, if the synchronization itself is not affected and the <code>quarantine</code> flag is set to <code>false</code>, the client may still indicate the issue once to the user in the background, e.g. as a balloontip notification.		Basically, there are two scenarios where either the errorneous version affects the synchronization state or not. For example, a file that was deleted at the client without sufficient permissions on the server can just be downloaded again by the client, and afterwards, client and server are in-sync again. On the other hand, e.g. when creating a new file at the client and this file can't be uploaded to the server due to missing permissions, the client is out of sync as long as the file is present. Therefore, the boolean parameter <code>quarantine</code> instructs the client whether the file or directory version must be excluded from the synchronization or not. If it is set to <code>true</code>, the client should exclude the version from the <code>clientVersions</code> array, and indicate the issue to the enduser. However, if the synchronization itself is not affected and the <code>quarantine</code> flag is set to <code>false</code>, the client may still indicate the issue once to the user in the background, e.g. as a balloontip notification.
Line 1,162:		Line 1,162:
	\| 750 \|\| previewLink \|\| String \|\| A direct link to a medium-sized preview image of the file if available.		\| 750 \|\| previewLink \|\| String \|\| A direct link to a medium-sized preview image of the file if available.
	\|-		\|-
	\| 751 \|\| directLinkFragments \|\| String \| The fragments part of the direct link that can be used in combination with the [~~[http~~://~~oxpedia~~.~~org~~/~~index.php?title=HTTP_API#Token_Login_.28since_7.0.1~~.~~29 \|~~token login]] method to jump directly to the detail view of the file in the web interface, bypassing the need to login manually.		\| 751 \|\| directLinkFragments \|\| String \| The fragments part of the direct link that can be used in combination with the [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (token login)] method to jump directly to the detail view of the file in the web interface, bypassing the need to login manually.
	\|-		\|-
	\| 752 \|\| directLink \|\| String \|\| A direct link to the detail view of the file in the web interface.		\| 752 \|\| directLink \|\| String \|\| A direct link to the detail view of the file in the web interface.
Line 1,391:		Line 1,391:

	Response:<br />		Response:<br />
	A JSON object containing details about the share link, including its URL, as described in [~~[HTTP_API#ShareLink\|Share Link]~~]. Additionally, the current checksum of the share target is included (starting with v7.8.1).		A JSON object containing details about the share link, including its URL, as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (share link)]. Additionally, the current checksum of the share target is included (starting with v7.8.1).

	{\| id="DriveShareTarget" cellspacing="0" border="1"		{\| id="DriveShareTarget" cellspacing="0" border="1"
Line 1,457:		Line 1,457:

	Request Body:<br />		Request Body:<br />
	A JSON object as described in [~~[HTTP_API#ShareLink\|Share Link]~~] containing the properties of the link to update, as well as the share target itself as described in [[#DriveShareTarget\|Drive Share Target]]. Only modified fields should be set.		A JSON object as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (share link)] containing the properties of the link to update, as well as the share target itself as described in [[#DriveShareTarget\|Drive Share Target]]. Only modified fields should be set.

	Response:<br />		Response:<br />
	A JSON object containing details about the share link, including its URL, as described in [~~[HTTP_API#ShareLink\|Share Link]~~]. Additionally, the current checksum of the share target is included (starting with v7.8.1).		A JSON object containing details about the share link, including its URL, as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (share link)]. Additionally, the current checksum of the share target is included (starting with v7.8.1).

	Example:		Example:
Line 1,849:		Line 1,849:

	Request body:<br />		Request body:<br />
	A JSON object named <code>folder</code> describing the updated folder metadata as described in [~~[HTTP_API#DetailedFolderData\|~~Detailed Folder Data]]. Currently, only the property <code>permissions</code> is considered. To notify added permission entities, an additional JSON object <code>notification</code> may be included, inside of which an optional <code>message</code> can be passed. To notify without a custom message, an empty <code>notification</code> object should still be added.		A JSON object named <code>folder</code> describing the updated folder metadata as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (Detailed Folder Data)]. Currently, only the property <code>permissions</code> is considered. To notify added permission entities, an additional JSON object <code>notification</code> may be included, inside of which an optional <code>message</code> can be passed. To notify without a custom message, an empty <code>notification</code> object should still be added.

	Response:<br />		Response:<br />
Line 1,898:		Line 1,898:

	Request body:<br />		Request body:<br />
	A JSON object named <code>file</code> describing the updated file metadata as described in [~~[HTTP_API#DetailedInfoitemData\|~~Detailed Infoitem Data]]. Currently, only the property <code>object_permissions</code> is considered. To notify added permission entities, an additional JSON object <code>notification</code> may be included, inside of which an optional <code>message</code> can be passed. To notify without a custom message, an empty <code>notification</code> object should still be added.		A JSON object named <code>file</code> describing the updated file metadata as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (Detailed Infoitem Data)]. Currently, only the property <code>object_permissions</code> is considered. To notify added permission entities, an additional JSON object <code>notification</code> may be included, inside of which an optional <code>message</code> can be passed. To notify without a custom message, an empty <code>notification</code> object should still be added.

	Response:<br />		Response:<br />
Line 2,046:		Line 2,046:

	Response:<br />		Response:<br />
	A JSON array holding the found users, contacts and groups. Each element is an object as described in [~~[HTTP_API#ExtendedPermissionObject \|~~ Extended Permission Object]], without the "bits" property set. For external contacts, the fields "entity" and "type" are also not set.		A JSON array holding the found users, contacts and groups. Each element is an object as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (Extended Permission Object)], without the "bits" property set. For external contacts, the fields "entity" and "type" are also not set.

	Example:		Example:
Line 2,447:		Line 2,447:
	\| checksum \|\| String \|\| The directory's checksum. Only set if metadata is not retrieved through [[#Metadata_Synchronization\|Metadata Synchronization]].		\| checksum \|\| String \|\| The directory's checksum. Only set if metadata is not retrieved through [[#Metadata_Synchronization\|Metadata Synchronization]].
	\|-		\|-
	\| own_rights \|\| Number\|\| Folder permissions which apply to the current user, as described in [~~[HTTP_API#PermissionFlags \|~~ Permission Flags]].		\| own_rights \|\| Number\|\| Folder permissions which apply to the current user, as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (Permission Flags)].
	\|-		\|-
	\| permissions \|\| Array \|\| All folder permissions, each element is an object as described in [~~[HTTP_API#PermissionObject \|~~ Permission Object]].		\| permissions \|\| Array \|\| All folder permissions, each element is an object as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (Permission Object)].
	\|-		\|-
	\| extended_permissions \|\| Array \|\| All folder permissions including some additional information, each element is an object as described in [~~[HTTP_API#ExtendedPermissionObject \|~~ Extended Permission Object]].		\| extended_permissions \|\| Array \|\| All folder permissions including some additional information, each element is an object as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (Extended Permission Object)].
	\|-		\|-
	\| default_folder \|\| Boolean \|\| <code>true</code> if the folder is a default folder, <code>false</code> or not set, otherwise.		\| default_folder \|\| Boolean \|\| <code>true</code> if the folder is a default folder, <code>false</code> or not set, otherwise.
Line 2,495:		Line 2,495:
	\| thumbnail \|\| String \|\| A URL to a thumbnail image for the file.		\| thumbnail \|\| String \|\| A URL to a thumbnail image for the file.
	\|-		\|-
	\| object_permissions \|\| Array \|\| All file permissions, each element is an object as described in [~~[#HTTP_API#ObjectPermissionObject \|~~ Object Permission Object]].		\| object_permissions \|\| Array \|\| All file permissions, each element is an object as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (Object Permission Object)].
	\|-		\|-
	\| extended_object_permissions \|\| Array \|\| All file permissions including some additional information, each element is an object as described in [~~[HTTP_API#ExtendedObjectPermissionObject \|~~ Extended Object Permission Object]].		\| extended_object_permissions \|\| Array \|\| All file permissions including some additional information, each element is an object as described in [https://documentation.open-xchange.com/latest/middleware/http_api.html HTTP API (Extended Object Permission Object)].
	\|-		\|-
	\| shared \|\| Boolean \|\| <code>true</code> if the file is shared, <code>false</code> or not set, otherwise.		\| shared \|\| Boolean \|\| <code>true</code> if the file is shared, <code>false</code> or not set, otherwise.

Tobias.friedrich at 14:11, 9 June 2016

2016-06-09T14:11:45Z

@@ Line 1,967: / Line 1,967: @@
 Available since API version 5. <br />
-Gets statistics about the trash folder contents.
+Gets statistics about the trash folder contents. <br />
 GET <code>/ajax/drive?action=trashStats</code>
@@ Line 2,006: / Line 2,007: @@
 Available since API version 5. <br />
-Empties the trash folder, i.e. permanently removes any contained files and folders.
+Empties the trash folder, i.e. permanently removes any contained files and folders. <br />
 GET <code>/ajax/drive?action=emptyTrash</code>
@@ Line 2,030: / Line 2,032: @@
+      }
 = File- and Directory Name Restrictions =

Tobias.friedrich at 07:40, 9 June 2016

2016-06-09T07:40:09Z

← Older revision		Revision as of 07:40, 9 June 2016
Line 1,963:		Line 1,963:
	}		}

			== Get trash folder statistics ==

			Available since API version 5. <br />

			Gets statistics about the trash folder contents.

			GET <code>/ajax/drive?action=trashStats</code>

			Parameters:
			* <code>session</code> - A session ID previously obtained from the login module.
			* <code>root</code> - The ID of the referenced root folder on the server.

			Response:<br />
			A JSON object holding the recursively accumulated folder statistics as described in [[#FolderStats\|Folder Statistics]] below. If no trash folder is available, an empty response is returned.

			{\| id="FolderStats" cellspacing="0" border="1"
			\|+ align="bottom" \| Folder Statistics
			! Name !! Type !! Value
			\|-
			\| totalSize \|\| Number \|\| The total size of the contents in bytes.
			\|-
			\| numFiles \|\| Number \|\| The total number of contained files.
			\|-
			\| numFolders \|\| Number \|\| The total number of contained folders.
			\|}

			Example:
			==> GET http://192.168.32.191/ajax/drive?action=trashStats&session=35d55f0bd2284e78a8eb4dba99b1310b&root=9542

			<== HTTP 200 OK (64.2423 ms elapsed, 67 bytes received)
			< Content:
			{
			"data": {
			"totalSize": 30904580,
			"numFiles": 39,
			"numFolders": 4
			}
			}

			== Empty trash folder ==

			Available since API version 5. <br />

			Empties the trash folder, i.e. permanently removes any contained files and folders.

			GET <code>/ajax/drive?action=emptyTrash</code>

			Parameters:
			* <code>session</code> - A session ID previously obtained from the login module.
			* <code>root</code> - The ID of the referenced root folder on the server.

			Response:<br />
			A JSON object holding the updated folder statistics after the trash was emptied as described in [[#FolderStats\|Folder Statistics]]. If no trash folder is available, an empty response is returned.

			Example:
			==> GET http://192.168.32.191/ajax/drive?action=emptyTrash&session=35d55f0bd2284e78a8eb4dba99b1310b&root=9542

			<== HTTP 200 OK (184.0234 ms elapsed, 52 bytes received)
			< Content:
			{
			"data": {
			"totalSize": 0,
			"numFiles": 0,
			"numFolders": 0
			}
			}


	= File- and Directory Name Restrictions =		= File- and Directory Name Restrictions =

Tobias.friedrich: /* edit */

2016-06-01T10:01:33Z

edit

← Older revision		Revision as of 10:01, 1 June 2016
Line 164:		Line 164:

	=== <code>edit</code> ===		=== <code>edit</code> ===
	Instructs the client to edit a file- or directory version. This is used for move/rename operations. The <code>version</code> parameter is set to the version as sent in the <code>clientVersions</code> array of the preceding <code>syncfiles</code>/</code>syncfolders</code> action. The <code>newVersion</code> contains the new name/path the client should use. Unless the optional boolean parameter <code>acknowledge</code> is set to <code>false</code> an <code>edit</code> action implies that the client updates its known versions store accordingly, i.e. removes the previous entry for <code>version</code> and adds a new entry for <code>newVersion</code>.		Instructs the client to edit a file- or directory version. This is used for move/rename operations. The <code>version</code> parameter is set to the version as sent in the <code>clientVersions</code> array of the preceding <code>syncfiles</code>/<code>syncfolders</code> action. The <code>newVersion</code> contains the new name/path the client should use. Unless the optional boolean parameter <code>acknowledge</code> is set to <code>false</code> an <code>edit</code> action implies that the client updates its known versions store accordingly, i.e. removes the previous entry for <code>version</code> and adds a new entry for <code>newVersion</code>.
	When editing a directory version, the client should implicitly take care to create any not exisiting subdirectories in the <code>path</code> of the <code>newVersion</code> parameter.		When editing a directory version, the client should implicitly take care to create any not exisiting subdirectories in the <code>path</code> of the <code>newVersion</code> parameter.
	A concurrent client-side modification of the file/directory version can be detected by the client by comparing the current checksum against the one in the passed <code>newVersion</code> parameter.		A concurrent client-side modification of the file/directory version can be detected by the client by comparing the current checksum against the one in the passed <code>newVersion</code> parameter.

Tobias.friedrich: /* Synchronize files in a folder */

2016-05-30T13:16:43Z

Synchronize files in a folder

← Older revision		Revision as of 13:16, 30 May 2016
Line 540:		Line 540:
	* <code>columns</code> (optional) - A comma-separated list of columns representing additional metadata that is relevant for the client. Each column is specified by a numeric column identifier. Column identifiers for file metadata are defined in [[#FileMetadata\|File Metadata]]. If available, the requested metadata of files is included in the corresponding <code>DOWNLOAD</code> and <code>ACKNOWLEDGE</code> actions (deprecated, available until API version 2).		* <code>columns</code> (optional) - A comma-separated list of columns representing additional metadata that is relevant for the client. Each column is specified by a numeric column identifier. Column identifiers for file metadata are defined in [[#FileMetadata\|File Metadata]]. If available, the requested metadata of files is included in the corresponding <code>DOWNLOAD</code> and <code>ACKNOWLEDGE</code> actions (deprecated, available until API version 2).
	* <code>pushToken</code> (optional) - The client's push registration token to associate it to generated events.		* <code>pushToken</code> (optional) - The client's push registration token to associate it to generated events.
	* <code>driveMeta</code> (optional, available since ~~v7.8.2~~) - Controls the <code>.drive-meta</code> synchronization mode: <code>true</code>/<code>false</code> to forcibly enable or disable metadata synchronization for the request, or <code>inline</code> to include <code>.drive-meta</code>-data inside a corresponding <code>DOWNLOAD</code> action as <code>data</code>-parameter.		* <code>driveMeta</code> (optional, available since API version 5) - Controls the <code>.drive-meta</code> synchronization mode: <code>true</code>/<code>false</code> to forcibly enable or disable metadata synchronization for the request, or <code>inline</code> to include <code>.drive-meta</code>-data inside a corresponding <code>DOWNLOAD</code> action as <code>data</code>-parameter if suitable.

	Request Body: <br />		Request Body: <br />
Line 548:		Line 548:

	Response: <br />		Response: <br />
	A JSON array containing all actions the client should execute for synchronization. Each array element is an action as described in [[#Actions \| Actions]]. <br /> If the <code>diagnostics</code> flag was set (either to <code>true</code> or <code>false</code>), this array is wrapped into an additional JSON object in the <code>actions</code> parameter, and the diagnostics trace is provided at <code>diagnostics</code>. <br /> If <code>driveMeta</code> was set to <code>inline</code>, <code>DOWNLOAD</code> actions for <code>.drive-meta</code> will carry the metadata in an additional JSON object in the corresponding action's parameters at <code>data</code>.		A JSON array containing all actions the client should execute for synchronization. Each array element is an action as described in [[#Actions \| Actions]]. <br /> If the <code>diagnostics</code> flag was set (either to <code>true</code> or <code>false</code>), this array is wrapped into an additional JSON object in the <code>actions</code> parameter, and the diagnostics trace is provided at <code>diagnostics</code>. <br /> If <code>driveMeta</code> was set to <code>inline</code>, <code>DOWNLOAD</code> actions for <code>.drive-meta</code> will carry the metadata in an additional JSON object in the corresponding action's parameters at <code>data</code>, if the <code>.drive-meta</code>-file is smaller than a certain threshold (the contents may still be requested with an explicit download then).

	Example:		Example: