[Buildbot] #2960: Builder page show that some build exists, but their own page doesn't

[Buildbot trac]

#2960: Builder page show that some build exists, but their own page doesn't
----------------------+-----------------------
Reporter:  Ben        |       Owner:  tardyp
    Type:  undecided  |      Status:  accepted
Priority:  major      |   Milestone:  0.9.0
 Version:  0.8.9      |  Resolution:
Keywords:  web        |
----------------------+-----------------------

Comment (by tardyp):

 I really dont think it is an architectural problem. It is just a
 implementation bug that needs to be solved. 404 error should go through
 the layers, and be changed to a proper exception, and retried at next
 bind() call

 You cannot cache a build at http level until it is actually complete, and
 most of the stuff user is actually interested in aren't finished, so this
 is why caching at this level is efficient. If you go from a running build
 page back to builder page, and then again back to the build page, you can
 see it is instant, and also, the build status has been updated in the
 background. I think this UX is very nice.

 You can for now try and see without the memoize, everything will work as
 expected, but the UI will feel a lot slower.

 If there is an architecture problem I would like to fix, it is the fact
 that collections are not handled properly. We store a representation of
 the list, and another representation for each item of the list, if
 requested independently.

 I would like to go even further, and store the cache in a browser backed
 db. This is one of my next project to actually rework completly the
 buildbot api.

 - Make it less generic, using coffeescript classes, especially for each
 resource type, have a method to know whether the resource is immutable (so
 that it can be cached permanantly, and update events subscribing is
 unneeded).

 - Make a separated bower library out of it, with fakes, so that it can be
 included in the plugins test dependancies. For now each plugins includes
 its own version of fakes for the buildbot service.

 - Use http://swagger.io/ for api description instead of current home
 backed "dataspec". This allows very nice api description UI:
 http://petstore.swagger.wordnik.com/

--
Ticket URL: <http://trac.buildbot.net/ticket/2960#comment:6>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation