MoleQueue: Difference between revisions

From wiki.openchemistry.org
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
MoleQueue is a Qt system tray resident application that integrates with desktop applications and HPC resources.
MoleQueue is a Qt system tray resident application that integrates with desktop applications and HPC resources.


== Get ChemData ==
== Get MoleQueue ==
The source code is available at [https://github.com/OpenChemistry/molequeue Github].
The source code is available at [https://github.com/OpenChemistry/molequeue Github].


Line 8: Line 8:
Image:MoleQueue_Screenshot.png
Image:MoleQueue_Screenshot.png
</gallery>
</gallery>
== JSON-RPC specification ==
The JSON-RPC specification is [http://json-rpc.org/wiki/specification here]. In a nutshell, the protocol consists of three message types: requests, responses, and notifications. Every request must be met with a reply, and a notification is simply a request with a <tt>null</tt> id.
Requests are JSON objects with three name/value pairs:
* <tt>method</tt> (String): The method requested.
* <tt>params</tt> (Array): An array of parameters for the requested method.
* <tt>id</tt> (Value): A unique identifier.
Each request is met with a reply of the following format:
* <tt>result</tt> (Object): The result of the request. Must be <tt>null</tt> if an error occurred.
* <tt>error</tt> (Object): A description of the error. Must be <tt>null</tt> if no error occurred.
* <tt>id</tt> (Value): Must be the same as the identifier used in the request.
As mentioned above, notifications follow the same format as requests, but use a <tt>null</tt> identifier.

Revision as of 11:09, 2 May 2012

MoleQueue is a Qt system tray resident application that integrates with desktop applications and HPC resources.

Get MoleQueue

The source code is available at Github.

Screenshots

JSON-RPC specification

The JSON-RPC specification is here. In a nutshell, the protocol consists of three message types: requests, responses, and notifications. Every request must be met with a reply, and a notification is simply a request with a null id.

Requests are JSON objects with three name/value pairs:

  • method (String): The method requested.
  • params (Array): An array of parameters for the requested method.
  • id (Value): A unique identifier.

Each request is met with a reply of the following format:

  • result (Object): The result of the request. Must be null if an error occurred.
  • error (Object): A description of the error. Must be null if no error occurred.
  • id (Value): Must be the same as the identifier used in the request.

As mentioned above, notifications follow the same format as requests, but use a null identifier.