foster/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-25 13:19:37 -05:00
Code Issues Wiki Activity
forgejo/vendor/github.com/couchbase/gomemcached
History
Lunny Xiao 15a475b7db
Fix recovery middleware to render gitea style page. (#13857) 
* Some changes to fix recovery

* Move Recovery to middlewares

* Remove trace code

* Fix lint

* add session middleware and remove dependent on macaron for sso

* Fix panic 500 page rendering

* Fix bugs

* Fix fmt

* Fix vendor

* recover unnecessary change

* Fix lint and addd some comments about the copied codes.

* Use util.StatDir instead of com.StatDir

Co-authored-by: 6543 <6543@obermui.de>
2021-01-05 21:05:40 +08:00
..
client Fix recovery middleware to render gitea style page. (#13857) 2021-01-05 21:05:40 +08:00
.gitignore Fix recovery middleware to render gitea style page. (#13857) 2021-01-05 21:05:40 +08:00
flexibleFraming.go chore: update github.com/couchbase/gomemcached and github.com/couchbase/go-couchbase (#9419) 2019-12-18 21:03:26 -05:00
go.mod Fix recovery middleware to render gitea style page. (#13857) 2021-01-05 21:05:40 +08:00
LICENSE add other session providers (#5963) 2019-02-05 11:52:51 -05:00
mc_constants.go Fix recovery middleware to render gitea style page. (#13857) 2021-01-05 21:05:40 +08:00
mc_req.go [Vendor] update macaron related (#13409) 2020-11-03 08:04:09 +02:00
mc_res.go Fix recovery middleware to render gitea style page. (#13857) 2021-01-05 21:05:40 +08:00
README.markdown Use Go1.11 module (#5743) 2019-03-27 19:15:23 +08:00
tap.go add other session providers (#5963) 2019-02-05 11:52:51 -05:00

README.markdown

gomemcached

This is a memcached binary protocol toolkit in 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

overview

The basic design can be seen in gocache. A storage server 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.