diff options
| author | Mura Li <typeless@users.noreply.github.com> | 2019-03-27 19:15:23 +0800 |
|---|---|---|
| committer | Lunny Xiao <xiaolunwen@gmail.com> | 2019-03-27 19:15:23 +0800 |
| commit | d77176912bccf1dc0ad93366df55f00fee23b498 (patch) | |
| tree | 309fc6350f77f4061360160b88343360d45d5d24 /vendor/github.com/couchbase/gomemcached | |
| parent | d578b71d61ee8131e8abf7f538b93d8c6cc6fe6d (diff) | |
| download | gitea-d77176912bccf1dc0ad93366df55f00fee23b498.tar.gz gitea-d77176912bccf1dc0ad93366df55f00fee23b498.zip | |
Use Go1.11 module (#5743)
* Migrate to go modules
* make vendor
* Update mvdan.cc/xurls
* make vendor
* Update code.gitea.io/git
* make fmt-check
* Update github.com/go-sql-driver/mysql
* make vendor
Diffstat (limited to 'vendor/github.com/couchbase/gomemcached')
| -rw-r--r-- | vendor/github.com/couchbase/gomemcached/.gitignore | 6 | ||||
| -rw-r--r-- | vendor/github.com/couchbase/gomemcached/README.markdown | 32 |
2 files changed, 38 insertions, 0 deletions
diff --git a/vendor/github.com/couchbase/gomemcached/.gitignore b/vendor/github.com/couchbase/gomemcached/.gitignore new file mode 100644 index 0000000000..f75d85a841 --- /dev/null +++ b/vendor/github.com/couchbase/gomemcached/.gitignore @@ -0,0 +1,6 @@ +#* +*.[68] +*~ +*.swp +/gocache/gocache +c.out diff --git a/vendor/github.com/couchbase/gomemcached/README.markdown b/vendor/github.com/couchbase/gomemcached/README.markdown new file mode 100644 index 0000000000..5e9b2de5be --- /dev/null +++ b/vendor/github.com/couchbase/gomemcached/README.markdown @@ -0,0 +1,32 @@ +# gomemcached + +This is a memcached binary protocol toolkit in [go][go]. + +It provides client and server functionality as well as a little sample +server showing how I might make a server if I valued purity over +performance. + +## Server Design + +<div> + <img src="http://dustin.github.com/images/gomemcached.png" + alt="overview" style="float: right"/> +</div> + +The basic design can be seen in [gocache]. A [storage +server][storage] is run as a goroutine that receives a `MCRequest` on +a channel, and then issues an `MCResponse` to a channel contained +within the request. + +Each connection is a separate goroutine, of course, and is responsible +for all IO for that connection until the connection drops or the +`dataServer` decides it's stupid and sends a fatal response back over +the channel. + +There is currently no work at all in making the thing perform (there +are specific areas I know need work). This is just my attempt to +learn the language somewhat. + +[go]: http://golang.org/ +[gocache]: gomemcached/blob/master/gocache/gocache.go +[storage]: gomemcached/blob/master/gocache/mc_storage.go |