bind: in the dial cache distinguish between direct and via cacheserver

In building a writeback DirServer cache, I require a process that can
make both cached and uncached calls to the StoreServer. The current
dial cache doesn't distinguish the two resulting in confusion. I
had already run into this in tests but had papered it ver by turning
off the dial cache. This provides a real solution, adding the

In so doing, I ended up rearranging code yet again, making
CacheEndpoint() once again a method of config. This was needed
to avoid import loops. It also got rid of the need to parse
the "cache" config variable on every Dial.

I also added a check to upspin/endpoint.go to check for
unassigned endpoints. I got tired of putting checks
against upspin.Endpont{} everywhere; not very obvious
what is being checked.

Change-Id: Icf68bc6400c3fc5532c928ef971d553d444f2847
Reviewed-by: Rob Pike <>
20 files changed
tree: 42c9a299caa243af3d7ab5035952653121b22ece
  1. .travis.yml
  6. Gopkg.lock
  7. Gopkg.toml
  10. README.binary
  12. access/
  13. bind/
  14. cache/
  15. client/
  16. cloud/
  17. cmd/
  18. config/
  19. dir/
  20. doc/
  21. errors/
  22. factotum/
  23. flags/
  24. key/
  25. log/
  26. metric/
  27. pack/
  28. path/
  29. rpc/
  30. serverutil/
  31. shutdown/
  32. store/
  33. subcmd/
  34. test/
  35. transports/
  36. upbox/
  37. upspin/
  38. user/
  39. valid/
  40. vendor/
  41. version/




About the project

Upspin is an experimental project to build a framework for naming and sharing files and other data securely, uniformly, and globally: a global name system of sorts.

It is not a file system, but a set of protocols and reference implementations that can be used to join things like file systems and other storage services to the name space.

Performance is not a primary goal. Uniformity and security are.

Upspin is not an official Google product.


Upspin has rough edges, and is not yet suitable for non-technical users.

Build Status


The code repository lives at and is mirrored to GitHub.

Note that the Upspin project does not use GitHub pull requests, and that we use the issue tracker for bug reports and proposals only.

See the Contribution Guidelines for more information on contributing to the project.

Reporting issues

Please report issues through our issue tracker.


All Upspin users should subscribe to the Upspin Announcements mailing list to receive critical information about the project.

Use the Upspin mailing list for discussion about Upspin use and development.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

The Upspin mascot is Copyright 2017 Renee French. All Rights Reserved.