A tracker for the LBRY protocol.
Go to file
2013-07-03 18:24:03 -04:00
config transactions, connpools, misc 2013-07-03 18:24:03 -04:00
example transactions, connpools, misc 2013-07-03 18:24:03 -04:00
server transactions, connpools, misc 2013-07-03 18:24:03 -04:00
storage transactions, connpools, misc 2013-07-03 18:24:03 -04:00
.travis.yml initial 2013-06-21 19:31:32 -04:00
AUTHORS initial 2013-06-21 19:31:32 -04:00
CONTRIBUTORS initial 2013-06-21 19:31:32 -04:00
LICENSE initial 2013-06-21 19:31:32 -04:00
main.go accidentally removed this err check 2013-06-24 00:18:59 -04:00
README.md grammar 2013-06-28 16:52:44 -04:00

#chihaya Build Status

chihaya is a high-performance BitTorrent tracker written in the Go programming language. It isn't quite ready for prime-time just yet, but these are the features that it targets:

  • Requests are multiplexed over all available threads
  • Low processing and memory footprint
  • IPv6 support
  • Generic storage interface that can be easily adapted to use any data store
  • Scaling properties that directly correlate with the chosen data store's scaling properties
  • Redis data storage driver

##installing

$ go install github.com/pushrax/chihaya

##configuring

Configuration is done in a JSON formatted file specified with the -config flag. One can start with example/config.json as a base.

##implementing custom storage

The storage package works similar to the standard library's database/sql package. To write a new storage backend, create a new Go package that has an implementation of both the Conn and the Driver interfaces. Within your package define an init() function that calls storage.Register(driverName, &yourDriver{}). Your driver must be thread-safe. After that, all you have to do is remember to add import _ path/to/your/library to the top of main.go and now config files will recognize your driver by name. If you're writing a driver for a popular data store, consider contributing it.

##contributing

If you're interested in contributing, please contact us in #chihaya on freenode(webchat) or post to the issue tracker. Please don't offer massive pull requests with no prior communication attempts (unannounced small changes are fine), as it will most likely lead to confusion and time wasted for everyone. And remember: good gophers always use gofmt!