Sugar Network/API: Difference between revisions

Line 186:

The reasons to proxy Sugar Network data on users side:

* Seamless support offline workflow;

* [[#Offline case|Seamless support]] offline workflow;

* ~~Provide user side features like cloning or launching software from the~~ Sugar Network.

* [[#Cloned resources|Easy download]] Sugar Network resources;

* [[#Launch activities|Reliable launch]] Sugar activities hosted on Sugar Network.

Proxying happens by providing the same Sugar Network API (with some extra functionality, see below) from

Line 228:

Line 229:

=== Launch activities ===

All activities can be launched as-is.

All Sugar Network activities can be launched as-is.

'''GET''' /context/''GUID''?cmd='''launch'''[&args=''ARG''][&activity_id=''ACTIVITY_ID''][&object_id=''OBJECT_ID''][&uri=''URI''][&color=''COLOR''][&no_spawn=''NO_SPAWN'']

Line 239:

Line 240:

* {{Code|NO_SPAWN}}, if specified, HTTP connection will not be closed until exiting activity process.

Previously cloned activities will be launched as-is from {{Code|~/Activities}} directory. The rest of activities will be downloaded from the server and kept in cache directory [with further garbage collecting].

Previously cloned activities will be launched as-is from {{Code|~/Activities}} directory. The rest of activities will be downloaded from the server and kept in cache directory [with further garbage collecting]. Besides, Sugar Network client application makes launch process reliable by solving software dependencies, e.g., missed packages will be installed using [[wikipedia:PackageKit|PackageKit]].

=== Access to the Journal ===

@@ Line 186: / Line 186: @@
 The reasons to proxy Sugar Network data on users side:
-* Seamless support offline workflow;
+* [[#Offline case|Seamless support]] offline workflow;
-* Provide user side features like cloning or launching software from the Sugar Network.
+* [[#Cloned resources|Easy download]] Sugar Network resources;
+* [[#Launch activities|Reliable launch]] Sugar activities hosted on Sugar Network.
 Proxying happens by providing the same Sugar Network API (with some extra functionality, see below) from
@@ Line 228: / Line 229: @@
 === Launch activities ===
-All activities can be launched as-is.
+All Sugar Network activities can be launched as-is.
   '''GET''' /context/''GUID''?cmd='''launch'''[&args=''ARG''][&activity_id=''ACTIVITY_ID''][&object_id=''OBJECT_ID''][&uri=''URI''][&color=''COLOR''][&no_spawn=''NO_SPAWN'']
@@ Line 239: / Line 240: @@
 * {{Code|NO_SPAWN}}, if specified, HTTP connection will not be closed until exiting activity process.
-Previously cloned activities will be launched as-is from {{Code|~/Activities}} directory. The rest of activities will be downloaded from the server and kept in cache directory [with further garbage collecting].
+Previously cloned activities will be launched as-is from {{Code|~/Activities}} directory. The rest of activities will be downloaded from the server and kept in cache directory [with further garbage collecting]. Besides, Sugar Network client application makes launch process reliable by solving software dependencies, e.g., missed packages will be installed using [[wikipedia:PackageKit|PackageKit]].
 === Access to the Journal ===