1. 20 May, 2015 5 commits
  2. 19 May, 2015 6 commits
  3. 18 May, 2015 7 commits
  4. 17 May, 2015 7 commits
  5. 15 May, 2015 1 commit
  6. 14 May, 2015 1 commit
  7. 13 May, 2015 2 commits
  8. 12 May, 2015 6 commits
    • Tim Groeneveld's avatar
    • Juan Batiz-Benet's avatar
      Merge pull request #1215 from eris-ltd/cors · ad9d84d5
      Juan Batiz-Benet authored
      Add CORS middleware handler to the API.
      ad9d84d5
    • Juan Batiz-Benet's avatar
      Merge pull request #1227 from ipfs/parallelize-handshake · 414ab636
      Juan Batiz-Benet authored
      net/p2p + secio: parallelize crypto handshake
      414ab636
    • Juan Batiz-Benet's avatar
      travis-ci: make test_all_commits · 482a492a
      Juan Batiz-Benet authored
      After losing jenkins, it's been difficult to test all commits
      manually. This commit adds a Makefile target that makes travis do it.
      Unfortunately, this is way too slow. It takes longer than the
      allotted 10min.
      
      After asking the travis people what to do, someone suggested making
      sure that each commit is pushed to github independently. This makes
      travis run CI on every single commit in the PR, and gives us nice
      status indicators on each one (so we know which ones did not pass).
      
      This approach means that we need to push a branch to the repo for
      each commit in the PR-- otherwise travis may cancel its run if it
      detects that the branch is no longer there. We could automate this
      with a bot that essentially does:
      
        for each PR:
          git fetch the PR branch
          push a branch per commit: <branch>-<commit>
      
        for each closed PR:
          delete all branches with pattern <branch>-<commit>
      482a492a
    • Juan Batiz-Benet's avatar
      Merge pull request #1221 from ipfs/unrestricted-api-access · 0c8a0975
      Juan Batiz-Benet authored
      Add option to allow unrestricted API access
      0c8a0975
    • Juan Batiz-Benet's avatar
      net/p2p + secio: parallelize crypto handshake · b84fa2b4
      Juan Batiz-Benet authored
      We had a very nasty problem: handshakes were serial so incoming
      dials would wait for each other to finish handshaking. this was
      particularly problematic when handshakes hung-- nodes would not
      recover quickly. This led to gateways not bootstrapping peers
      fast enough.
      
      The approach taken here is to do what crypto/tls does:
      defer the handshake until Read/Write[1]. There are a number of
      reasons why this is _the right thing to do_:
      - it delays handshaking until it is known to be necessary (doing io)
      - it "accepts" before the handshake, getting the handshake out of the
        critical path entirely.
      - it defers to the user's parallelization of conn handling. users
        must implement this in some way already so use that, instead of
        picking constants surely to be wrong (how many handshakes to run
        in parallel?)
      
      [0] http://golang.org/src/crypto/tls/conn.go#L886
      b84fa2b4
  9. 11 May, 2015 1 commit
  10. 10 May, 2015 4 commits