Changes

Jump to navigation Jump to search
No change in size ,  23:23, 30 May 2013
Line 253: Line 253:  
== Usage ==
 
== Usage ==
   −
Being HTTP based, Sugar Network API can be used in any manner regular HTTP requests can be handled. But for command-line access, there is a handy tool, {{Code|sugar-network}}, that takes care about Sugar Network specific like launching local API (if it is not already available) to get access to [[#Client_proxy|local proxy]].
+
Being HTTP based, Sugar Network API can be used in any manner regular HTTP requests can be handled. But for command-line access, there is a handy tool, {{Code|sugar-network}}, which takes care about Sugar Network specific like launching local API (if it is not already available) to get access to [[#Client_proxy|local proxy]].
    
The sugar-network command-line format is below. Call {{Code|sugar-network --help}} for more detailed info.
 
The sugar-network command-line format is below. Call {{Code|sugar-network --help}} for more detailed info.
Line 262: Line 262:  
* {{Code|ARG<nowiki>=</nowiki>VALUE}}, request arguments as they being passed to in url.
 
* {{Code|ARG<nowiki>=</nowiki>VALUE}}, request arguments as they being passed to in url.
   −
{{Code|POST}} and {{Code|PUT}} commands require data to pass, pass the following command-line arguments:
+
{{Code|POST}} and {{Code|PUT}} commands require data to pass, use the following command-line arguments:
    
* {{Code|-f FILE}} to specify the file to pass;
 
* {{Code|-f FILE}} to specify the file to pass;

Navigation menu