Difference between revisions of "AurJson"

From ArchWiki
Jump to: navigation, search
m (codeline -> ic)
Line 1: Line 1:
[[Category: Package management (English)]]
+
[[Category:Package management]]
 
The '''AurJson''' interface is a lightweight remote interface for the [[AUR]]. It utilizes http GET queries as the request format, and [http://www.json.org/ json] as the response data exchange format.
 
The '''AurJson''' interface is a lightweight remote interface for the [[AUR]]. It utilizes http GET queries as the request format, and [http://www.json.org/ json] as the response data exchange format.
  

Revision as of 15:48, 23 April 2012

The AurJson interface is a lightweight remote interface for the AUR. It utilizes http GET queries as the request format, and json as the response data exchange format.

API Usage

The RPC interface has four major query types:

  • search
  • info
  • multiinfo
  • msearch

Each method requires the following HTTP GET syntax:

type=methodname&arg=data

Where methodname is the name of an allowed method, and data is the argument to the call.

Data is returned in json encapsulated format.

Query Types

As noted above, there are four query types:

  • search
  • info
  • msearch
  • msearch

Search

A search type query takes an argument of a string, or partial string, with which to perform a package search. Possible return types are error and search.

Example:

http://aur-url/rpc.php?type=search&arg=foobar

The above is a query of type search and the search argument is "foobar".

Info

An info type query takes an argument of a string or an integer. If an integer, the integer must be an exact match to an existing packageID, or an error type is returned. If a string, the string must be an exact match to an existing packageName, or an error type is returned.

Examples:

http://aur-url/rpc.php?type=info&arg=1123
http://aur-url/rpc.php?type=info&arg=foobar

The two examples above are both queries of type info. The first query is using an integer type argument, and the second is using a packageName argument. If packageID 1123 corresponded to packageName foobar, then both of the above queries would return the details of the foobar package.

mutiinfo

The majority of "real world" info requests come in hefty batches. AUR can handle these in one request rather than multiple by allowing AUR clients to send multiple arguments.

Examples:

http://aur.test/rpc.php?type=multiinfo&arg[]=cups-xerox&arg[]=cups-mc2430dl&arg[]=10673

msearch

A msearch type query takes an argument of a string, or partial string, with which to perform a search by maintainer name. Possible return types are error and msearch.

Example:

http://aur-url/rpc.php?type=msearch&arg=cactus

The above is a query of type msearch and the search argument is "cactus".

Return Types

The return payload is of one format, and currently has three main types.

The format of the return payload is:

{"type":ReturnType,"results":ReturnData}

ReturnType is a string, and the value is one of:

* error
* search
* info

The type of ReturnData is dependent on the query type:

  • If ReturnType is error then ReturnData is a string.
  • If ReturnType is search then ReturnData is an array of dictionary objects.
  • If ReturnType is info then ReturnData is a single dictionary object.

Error

The error type has an error response string as the return value. An error response can be returned from either a search or an info query type.

Example of ReturnType error:

{"type":"error","results":"No results found"}

Search

The search type is the result returned from a search request operation. Returning the type as search is useful for detecting whether the response to a search operation is search data or an error.

Example of ReturnType search:

{"type":"search","results":[{"Name":"pam_abl","ID":"1995"}]}

Info

The info type is the result returned from an info request operation. Returning the type as search is useful for detecting whether the response to a search operation is search data or an error.

Example of ReturnType info:

 {
    "type": "info",
    "results": {
        "Description": "Provides auto blacklisting of hosts and users responsible for repeated failed authentication attempts", 
        "ID": "1995", 
        "License": "", 
        "Name": "pam_abl", 
        "NumVotes": "4", 
        "OutOfDate": "0", 
        "URL": "http://www.hexten.net/pam_abl",  
        "URLPath": "/packages/pam_abl/pam_abl.tar.gz", 
        "Version": "0.2.3-1"
    }
 }
 

jsonp

If you are working with a javascript page, and need a json callback mechanism, you can do it. You just need to provide an additional callback variable. This callback is usually handled via the javascript library, but here is an example.

Example Query:

http://aur-url/rpc.php?type=search&arg=foobar&callback=jsonp1192244621103

Example Result:

jsonp1192244621103({"type":"error","results":"No results found"})

This would automatically call the JavaScript function jsonp1192244621103 with the parameter set to the results of the RPC call. (In this case, {"type":"error","results":"No results found"})

More Examples

Example Query and Result:

 http://aur-url/rpc.php?type=search&arg=foobar
 {"type":"error","results":"No results found"}
 

Example Query and Result:

 http://aur-url/rpc.php?type=search&arg=pam_abl
 {"type":"search","results":[{"Name":"pam_abl","ID":"1995"}]}
 

Example Query and Result:

 http://aur-url/rpc.php?type=info&arg=pam_abl
 {
    "type": "info",
    "results": {       
        "Description": "Provides auto blacklisting of hosts and users responsible for repeated failed authentication attempts", 
        "ID": "1995", 
        "License": "", 
        "Name": "pam_abl", 
        "NumVotes": "4",
        "OutOfDate": "0",
        "URL": "http://www.hexten.net/pam_abl",
        "URLPath": "/packages/pam_abl/pam_abl.tar.gz",
        "Version": "0.2.3-1"
    }
 }
 

Reference Clients

Sometimes things are easier to understand with examples. A few reference implementations (jQuery, python, ruby) are available at the following url: https://github.com/cactus/random/tree/master/aurjson_examples