Skip to content

GitLab

Switch branch/tag
  1. 09 Mar, 2016 1 commit
  3. 13 Feb, 2016 3 commits
  5. 11 Feb, 2016 4 commits
  7. 31 Jan, 2016 2 commits
  9. 30 Jan, 2016 3 commits
  11. 29 Jan, 2016 1 commit
  13. 14 Jan, 2016 1 commit
  15. 12 Jan, 2016 1 commit
  17. 05 Jan, 2016 2 commits
  19. 05 Nov, 2015 1 commit
  21. 02 Nov, 2015 1 commit
  23. 27 Oct, 2015 1 commit
  25. 03 Oct, 2015 1 commit
  27. 02 Oct, 2015 1 commit
  29. 01 Oct, 2015 1 commit
  31. 30 Sep, 2015 1 commit
  33. 29 Sep, 2015 2 commits
    • Jeromy's avatar
      Implement ipns republisher · 815a031f
      Jeromy authored 
      This commit adds a very basic process that will periodically go through
a list of given ids and republish the values for their ipns entries.

License: MIT
Signed-off-by: default avatarJeromy <jeromyj@gmail.com>
      815a031f
    • Jeromy's avatar
      ipns record selection via sequence numbers · cfcc3d6a
      Jeromy authored 
      This commit adds a sequence number to the IpnsEntry protobuf
that is used to determine which among a set of entries for the same key
is the 'most correct'.

GetValues has been added to the routing interface to retrieve a set of
records from the dht, for the caller to select from.

GetValue (singular) will call GetValues, select the 'best' record, and
then update that record to peers we received outdated records from.
This will help keep the dht consistent.

License: MIT
Signed-off-by: default avatarJeromy <jeromyj@gmail.com>
      cfcc3d6a
  35. 15 Sep, 2015 1 commit
  37. 23 Aug, 2015 1 commit
  39. 10 Jul, 2015 1 commit
  41. 01 Jun, 2015 1 commit
  43. 20 May, 2015 7 commits
    • W. Trevor King's avatar
      namesys/namesys_test: Excercise mpns.ResolveN · ce015d24
      W. Trevor King authored 
      Shifting the generic testResolution helper from the protocol-specific
dns_test.go to the generic namesys_test.go.
      ce015d24
    • W. Trevor King's avatar
      namesys/dns_test: Add DNS resolution tests with a mock resolver · c9fceeb1
      W. Trevor King authored
      c9fceeb1
    • 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
    • W. Trevor King's avatar
      namesys/dns: Use SplitN to find dnslink references · 04a96983
      W. Trevor King authored 
      RFC 6763 requires printable ASCII except '=' for the key [1], but
allows any character including '=' in the value [2].  This patch
adjusts our parsing to avoid splitting on '=' in the value, and then
ignoring anything after that split.

[1]: https://tools.ietf.org/html/rfc6763#section-6.4
[2]: https://tools.ietf.org/html/rfc6763#section-6.5
      04a96983
    • W. Trevor King's avatar
      namesys/interface: Expand package docs to discuss mutable names · 03260a92
      W. Trevor King authored 
      What they are, why you'd use them, and which command-line tools you
can use to access this functionality.
      03260a92
    • W. Trevor King's avatar
      namesys/publisher: Drop the 'namesys: ' prefix for the Publish log · 02cb5f3b
      W. Trevor King authored 
      This is already handled by setup in namesys/routing.go:

  var log = u.Logger("namesys")
      02cb5f3b
  45. 28 Apr, 2015 1 commit
  47. 27 Apr, 2015 1 commit