Platform Team/Server Kit/sugar-server: Difference between revisions

Line 28:

* {{Code|success: OK}};

* ~~Several keys~~ that are mapped 1:1 as configuration options of the sugar-client utility. The particular set of keys are details of implementations and processed only internally;

* {{Code|config}} key with dictionary of values that are mapped 1:1 as configuration options of the sugar-client utility. The particular set of keys are details of implementations and processed only internally;

* [http://wiki.laptop.org/go/School_server OLPC XS] backwards compatibility keys that are not being processed by sugar-client: {{Code|backupurl}}, {{Code|jabberserver}}, {{Code|backuppath}}.

Line 54:

* Various error codes on fails with error message as HTML content.

If backup is available, client will start transfering Journal files using Rsync url that was gotten while registration via Id service. The ~~particular details are not an object of public interface and depends~~ on ~~sugar-~~client ~~and backup service implementation~~, ~~but~~ process is fully server driven.

If backup is available, client will start transfering Journal files using Rsync url that was gotten while registration via Id service. The Rsync url is being used without any modifications on a client side, i.e., the process is fully server driven.

=== activation ===

@@ Line 28: / Line 28: @@
 * {{Code|success: OK}};
-* Several keys that are mapped 1:1 as configuration options of the sugar-client utility. The particular set of keys are details of implementations and processed only internally;
+* {{Code|config}} key with dictionary of values that are mapped 1:1 as configuration options of the sugar-client utility. The particular set of keys are details of implementations and processed only internally;
 * [http://wiki.laptop.org/go/School_server OLPC XS] backwards compatibility keys that are not being processed by sugar-client: {{Code|backupurl}}, {{Code|jabberserver}}, {{Code|backuppath}}.
@@ Line 54: / Line 54: @@
 * Various error codes on fails with error message as HTML content.
-If backup is available, client will start transfering Journal files using Rsync url that was gotten while registration via Id service. The particular details are not an object of public interface and depends on sugar-client and backup service implementation, but process is fully server driven.
+If backup is available, client will start transfering Journal files using Rsync url that was gotten while registration via Id service. The Rsync url is being used without any modifications on a client side, i.e., the process is fully server driven.
 === activation ===