Skip to content

GitLab

Switch branch/tag
  1. 14 Dec, 2016 1 commit
  3. 13 Dec, 2016 2 commits
  5. 29 Nov, 2016 1 commit
  7. 16 Nov, 2016 1 commit
  9. 28 Oct, 2016 1 commit
  11. 25 Oct, 2016 1 commit
  13. 10 Oct, 2016 1 commit
    • Jeromy's avatar
      bitswap: protocol extension to handle cids · f4d7369c
      Jeromy authored 
      This change adds the /ipfs/bitswap/1.1.0 protocol. The new protocol
adds a 'payload' field to the protobuf message and deprecates the
existing 'blocks' field. The 'payload' field is an array of pairs of cid
prefixes and block data. The cid prefixes are used to ensure the correct
codecs and hash functions are used to handle the block on the receiving
end.

License: MIT
Signed-off-by: default avatarJeromy <why@ipfs.io>
      f4d7369c
  15. 06 Oct, 2016 1 commit
  17. 26 Sep, 2016 1 commit
  19. 20 Sep, 2016 1 commit
  21. 09 Sep, 2016 1 commit
  23. 26 Aug, 2016 1 commit
  25. 20 Aug, 2016 1 commit
  27. 26 Jul, 2016 1 commit
  29. 02 Jul, 2016 1 commit
  31. 01 Jul, 2016 1 commit
  33. 24 Jun, 2016 1 commit
  35. 12 Jun, 2016 2 commits
  37. 17 Apr, 2016 2 commits
  39. 11 Apr, 2016 1 commit
  41. 07 Apr, 2016 1 commit
  43. 30 Mar, 2016 1 commit
  45. 09 Mar, 2016 1 commit
  47. 31 Jan, 2016 2 commits
  49. 30 Jan, 2016 2 commits
  51. 12 Jan, 2016 1 commit
  53. 05 Jan, 2016 2 commits
  55. 02 Nov, 2015 1 commit
  57. 02 Oct, 2015 1 commit
  59. 30 Sep, 2015 1 commit
  61. 20 May, 2015 2 commits
    • W. Trevor King's avatar
      namesys/dns: Pluggable lookupTXT field · 1e6594d0
      W. Trevor King authored 
      So we can attach a mock lookup function for testing.
      1e6594d0
    • W. Trevor King's avatar
      namesys: Add recursive resolution · 3ead2443
      W. Trevor King authored 
      This allows direct access to the earlier protocol-specific Resolve
implementations.  The guts of each protocol-specific resolver are in
the internal resolveOnce method, and we've added a new:

  ResolveN(ctx, name, depth)

method to the public interface.  There's also:

  Resolve(ctx, name)

which wraps ResolveN using DefaultDepthLimit.  The extra API endpoint
is intended to reduce the likelyhood of clients accidentally calling
the more dangerous ResolveN with a nonsensically high or infinite
depth.  On IRC on 2015-05-17, Juan said:

15:34 <jbenet> If 90% of uses is the reduced API with no chance to
  screw it up, that's a huge win.
15:34 <wking> Why would those 90% not just set depth=0 or depth=1,
  depending on which they need?
15:34 <jbenet> Because people will start writing `r.Resolve(ctx, name,
  d)` where d is a variable.
15:35 <wking> And then accidentally set that variable to some huge
  number?
15:35 <jbenet> Grom experience, i've seen this happen _dozens_ of
  times. people screw trivial things up.
15:35 <wking> Why won't those same people be using ResolveN?
15:36 <jbenet> Because almost every example they see will tell them to
  use Resolve(), and they will mostly stay away from ResolveN.

The per-prodocol versions also resolve recursively within their
protocol.  For example:

  DNSResolver.Resolve(ctx, "ipfs.io", 0)

will recursively resolve DNS links until the referenced value is no
longer a DNS link.

I also renamed the multi-protocol ipfs NameSystem (defined in
namesys/namesys.go) to 'mpns' (for Multi-Protocol Name System),
because I wasn't clear on whether IPNS applied to the whole system or
just to to the DHT-based system.  The new name is unambiguously
multi-protocol, which is good.  It would be nice to have a distinct
name for the DHT-based link system.

Now that resolver output is always prefixed with a namespace and
unprefixed mpns resolver input is interpreted as /ipfs/,
core/corehttp/ipns_hostname.go can dispense with it's old manual
/ipfs/ injection.

Now that the Resolver interface handles recursion, we don't need the
resolveRecurse helper in core/pathresolver.go.  The pathresolver
cleanup also called for an adjustment to FromSegments to more easily
get slash-prefixed paths.

Now that recursive resolution with the namesys/namesys.go composite
resolver always gets you to an /ipfs/... path, there's no need for the
/ipns/ special case in fuse/ipns/ipns_unix.go.

Now that DNS links can be things other than /ipfs/ or DHT-link
references (e.g. they could be /ipns/<domain-name> references) I've
also loosened the ParsePath logic to only attempt multihash validation
on IPFS paths.  It checks to ensure that other paths have a
known-protocol prefix, but otherwise leaves them alone.

I also changed some key-stringification from .Pretty() to .String()
following the potential deprecation mentioned in util/key.go.
      3ead2443
  63. 27 Apr, 2015 1 commit
  65. 31 Mar, 2015 1 commit