Changes

The reasons to proxy Sugar Network data on users side:

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

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

=== Launch activities ===

=== 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'']

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

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

* {{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 ===

=== Access to the Journal ===