Juan Batiz-Benet 4807127def net: move Network implementation to own pkg ... I needed the network implementation in its own package, because I'll be writing several services that will plug into _it_ that shouldn't be part of the core net package. and then there were dependency conflicts. yay. mux + identify are good examples of what i mean.		2015-01-02 08:46:43 -08:00
..
interface.go	doc: specify iteration order randomization	2014-12-28 06:51:33 -05:00
mock_conn.go	net: move Network implementation to own pkg	2015-01-02 08:46:43 -08:00
mock_link.go	peer change: peer.Peer -> peer.ID	2014-12-23 08:33:32 -08:00
mock_net.go	clean up test setup interface	2015-01-02 08:33:42 +00:00
mock_peernet.go	net: move Network implementation to own pkg	2015-01-02 08:46:43 -08:00
mock_printer.go	mocknet printer for printing	2014-12-17 23:25:41 -08:00
mock_stream.go	mv net/mock2 -> net/mock	2014-12-17 23:25:40 -08:00
mock_test.go	peer change: peer.Peer -> peer.ID	2014-12-23 08:33:32 -08:00
mock.go	mocknet: FullMesh connects to self too.	2014-12-17 23:25:40 -08:00