Changes between Version 5 and Version 6 of DevelopmentPlan


Ignore:
Timestamp:
11/05/10 06:50:42 (3 years ago)
Author:
dustin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentPlan

    v5 v6  
    2525== Web Status to new API == 
    2626 
    27 Rather than redevelop the existing, templated web status using a new Python API (which would entail a complete rewrite), the new web status will be written in !JavaScript, which can be served statically -- either by Buildbot or any other web service.  It will use the JSONRPC interface to get the data it needs and render it in the browser.  This is a critical step before beginning work on the statusdb, as the existing template system makes heavy use of synchronous status-fetching methods. 
     27Rather than redevelop the existing, templated web status using a new Python API (which would entail a complete rewrite), the new web status will be written in !JavaScript, which can be served statically -- either by Buildbot or any other web service.  It will use the JSONRPC interface to get the data it needs and render it in the browser.  This is a critical step before beginning work on the statusdb, as the existing template system makes heavy use of synchronous status-fetching methods.  Open questions: 
     28 * what !JavaScript library can we use?  How does licensing limit our choices? 
    2829 
    2930== IRC ==