fd9b03a431
Rather than spawning a new goroutine for each message, run each log system in a dedicated goroutine. Ensure that logging is still asynchronous by using a per-system buffer (currently 500 messages). If it overflows all logging will hang, but that's better than spawning indefinitely many goroutines. |
||
|---|---|---|
| ethchain | ||
| ethcrypto | ||
| ethdb | ||
| ethlog | ||
| ethminer | ||
| ethpipe | ||
| ethrpc | ||
| ethstate | ||
| ethtrie | ||
| ethutil | ||
| ethvm | ||
| ethwire | ||
| event | ||
| pow/ar | ||
| tests | ||
| types | ||
| websocket | ||
| .gitignore | ||
| .travis.yml | ||
| LICENSE | ||
| README.md | ||
| block_pool.go | ||
| ethereum.go | ||
| events.go | ||
| nat.go | ||
| natpmp.go | ||
| natupnp.go | ||
| peer.go | ||
README.md
Ethereum
Ethereum Go Development package (C) Jeffrey Wilcke
Ethereum is currently in its testing phase. The current state is "Proof of Concept 0.6.5". For build instructions see the Wiki.
Ethereum Go is split up in several sub packages Please refer to each individual package for more information.
The eth is the top-level package of the Ethereum protocol. It functions as the Ethereum bootstrapping and peer communication layer. The ethchain contains the Ethereum blockchain, block manager, transaction and transaction handlers. The ethwire contains the Ethereum wire protocol which can be used to hook in to the Ethereum network. ethutil contains utility functions which are not Ethereum specific. The utility package contains the patricia trie, RLP Encoding and hex encoding helpers. The ethdb package contains the LevelDB interface and memory DB interface.
This is the bootstrap package. Eth-go contains all the necessary code to get a node and connectivity going.
Build
This is the Developer package. For the Ethereal client please see Ethereum(G).
go get -u github.com/ethereum/eth-go
Contribution
If you'd like to contribute to Eth please fork, fix, commit and
send a pull request. Commits who do not comply with the coding standards
are ignored (use gofmt!). If you send pull requests make absolute sure that you
commit on the develop branch and that you do not merge to master.
Commits that are directly based on master are simply ignored.
To make life easier try git flow it sets this all up and streamlines your work flow.
Coding standards
Sources should be formatted according to the Go Formatting Style.
Unless structs fields are supposed to be directly accesible, provide Getters and hide the fields through Go's exporting facility.
When you comment put meaningfull comments. Describe in detail what you want to achieve.
wrong
// Check if the value at x is greater than y
if x > y {
// It's greater!
}
Everyone reading the source probably know what you wanted to achieve with above code. Those are not meaningful comments.
While the project isn't 100% tested I want you to write tests non the less. I haven't got time to evaluate everyone's code in detail so I expect you to write tests for me so I don't have to test your code manually. (If you want to contribute by just writing tests that's fine too!)