User:Jskladan/Sandbox:Reading ResultsDB Code

From FedoraProject

< User:Jskladan
Revision as of 13:03, 22 January 2014 by Jskladan (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
QA.png


Warning (medium size).png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
Idea.png
ResultsDB Overview
If you want to know what is ResultsDB, jump here: ResultsDB_Overview

Contents

Refs

How to read ResultsDB Code

ResultsDB is written using TurboGears2 Web Framework, which has quite awesome documentation itself [2], so I won't go into much detail, but just pass links to the appropriate parts of the documentation.

Directory Structure

Detailed information about the directory structure can be found in the TG2.1 Docs [3]. For ResultsDB, the interesting stuff happens in controllers and model.

Controllers/root.py

This is the 'center point' of all the ResultsDB functionality, that is the XMLRPC interface.

class RootController(BaseController)

Server as the 'wrapper' for the xmlrpc controller. It can also provide functionality for web interface, if we ever decide that ResultsDB should have a 'native' one and not just standalone frontends.

class XmlRpcController(XMLRPCController, InputApi, OutputApi)

Just an 'aggregation' class, which provides the XMLRPC interface (XMLRPCControlled), and also the methods for storing (InputApi) or retrieving (OutputApi) data to/from ResultsDB.

class InputApi(object)

Implementation of the API for storing data in ResultsDB. More information[4].

class OutputApi(object)

Placeholder for the future implementation.

Model

Links

  1. http://git.fedorahosted.org/git/?p=ResultsDB.git
  2. 2.0 2.1 http://www.turbogears.org/2.1/docs/
  3. 3.0 3.1 http://www.turbogears.org/2.1/docs/main/explorequickstart.html
  4. 4.0 4.1 https://fedoraproject.org/wiki/AutoQA_resultsdb_API