1. 21 Nov, 2018 1 commit
  2. 23 Apr, 2018 1 commit
    • Marek Vavruša's avatar
      add bindings for the checkout layer · 98c8d353
      Marek Vavruša authored
      This one was missing from the current bindings. The checkout layer
      runs when the worker attempts to send a DNS query to given upstream
      when the address is already determined. The layer can add EDNS options
      or update outbound query, or block particular addresses / protocol.
      98c8d353
  3. 16 Nov, 2017 1 commit
    • Vladimír Čunát's avatar
      rename module 'cache_lmdb' -> 'cache' · dfe7468d
      Vladimír Čunát authored
      The name was weird.  There's no other implementation ATM and the module
      will always be only really suitable for *local* caches, but otherwise
      it's not neccessarily bound to LMDB.
      dfe7468d
  4. 26 May, 2017 1 commit
  5. 28 Feb, 2017 1 commit
  6. 16 Feb, 2017 1 commit
  7. 26 Jan, 2017 1 commit
  8. 25 Jan, 2017 1 commit
  9. 08 Nov, 2016 2 commits
    • Vladimír Čunát's avatar
      layer: refactor and better describe the API · cc47973e
      Vladimír Čunát authored
      - The API and ABI for modules changes slightly (details below).
        KR_MODULE_API is bumped to avoid loading incompatible code.
        We have bumped libkres ABIVER since the last release 1.1.1,
        so leaving that one intact.
      
      - Make KR_STATE_YIELD not reuse 0 value anymore.
        It's easy to e.g. return kr_ok() by mistake.
      - struct kr_layer_t:
        * ::mm was unused, uninitialized, etc.
        * Make ::state an int, as it was everywhere else.
        * void *data was ugly and always containing struct kr_request *
      - struct kr_layer_api:
        * Drop the void* parameter from ::begin, as it was only used
          for the request which is available as ctx->req anyway
          (formerly ctx->data).
        * Drop ::fail.  It wasn't even called.  Modules can watch for
          KR_STATE_FAIL in ::finish.
      - Document the apparent meaning of the layer interface, deduced mainly
        from the way it's used in the code.  Caveats:
        * enum knot_layer_state handling seems to assume that it holds exactly
          one of the possibilities at a time.  The cookie module does NOT
          follow that (intentionally), apparently depending on the exact
          implementation of the handling at that moment.  It feels fragile.
        * I was unable to deduce a plausible description of when ::reset is
          called.  It's practically unused in modules, too.
      cc47973e
    • Vladimír Čunát's avatar
      layer: rename knot_ identifiers that are private now · 4ad98bff
      Vladimír Čunát authored
      It causes lots of line changes, but it would be confusing to keep the
      current state over long term.
      4ad98bff
  10. 16 Jul, 2016 1 commit
  11. 12 Jul, 2016 1 commit
  12. 16 Jun, 2016 1 commit
  13. 10 Dec, 2015 1 commit
  14. 25 Nov, 2015 1 commit
  15. 06 May, 2015 1 commit
  16. 22 Apr, 2015 1 commit
  17. 13 Apr, 2015 1 commit
  18. 10 Apr, 2015 1 commit
  19. 29 Mar, 2015 1 commit
  20. 27 Mar, 2015 1 commit
  21. 19 Mar, 2015 1 commit
  22. 18 Mar, 2015 1 commit
  23. 10 Mar, 2015 1 commit
  24. 23 Feb, 2015 2 commits