Skip to content
Snippets Groups Projects
  1. Jun 01, 2012
    • Monty Brandenberg's avatar
      Major steps towards implementing the policy component. · b8edacd0
      Monty Brandenberg authored
      Identified and reacted to the priority inversion problem we
      have in texturefetch.  Includes the introduction of a priority_queue
      for the requests that are ready.  Start some parameterization in
      anticipation of having policy_class everywhere.  Removed _assert.h
      which isn't really needed in indra codebase.  Implemented async
      setPriority request (which I hope I can get rid of eventually along
      with all priorities in this library).  Converted to using unsigned
      int for priority rather than float.  Implemented POST and did
      groundwork for PUT.
      b8edacd0
  2. May 23, 2012
    • Monty Brandenberg's avatar
      Integrate llcorehttp library into lltexturefetch design. · 8fc35012
      Monty Brandenberg authored
      This is the first functional viewer pass with the HTTP work of the texture fetch
      code performed by the llcorehttp library.  Not exactly a 'drop-in' replacement
      but a work-alike with some changes (e.g. handler notification in consumer
      thread versus responder notification in worker thread).
      
      This also includes some temporary changes in the priority scheme to prevent
      the kind of priority inversion found in VWR-28996.  Scheme used here does
      provide liveness if not optimal responsiveness or order-of-operation.
      
      The llcorehttp library at this point is far from optimally performing.
      Its worker thread is making relatively poor use of cycles it gets and
      it doesn't idle or sleep intelligently yet.  This early integration step
      helps shake out the interfaces, implementation niceties will be covered
      soon.
      8fc35012
  3. May 07, 2012
    • Monty Brandenberg's avatar
      Build llcorehttp as part of a viewer dependency with unit tests. This required · 74d59e71
      Monty Brandenberg authored
      boost::thread and the easiest path to that was to go with the 1.48 Boost release
      in the 3P tree (eliminating a fork for a modified 1.45 packaging).  One unit test,
      the most important one, is failing in test_httprequest but that can be attended
      to later.  This test issues a GET to http://localhost:2/ and that is hitting the
      wire but the libcurl plumbing isn't delivering the failure, only the eventual
      timeout.  An unexpected change in behavior.
      74d59e71
  4. Apr 25, 2012
  5. Apr 23, 2012
Loading