History

Harshavardhana 61175ef091 Migrate to govendor to avoid limitations of godep - over the course of a project history every maintainer needs to update its dependency packages, the problem essentially with godep is manipulating GOPATH - this manipulation leads to static objects created at different locations which end up conflicting with the overall functionality of golang. This also leads to broken builds. There is no easier way out of this other than asking developers to do 'godep restore' all the time. Which perhaps as a practice doesn't sound like a clean solution. On the other hand 'godep restore' has its own set of problems. - govendor is a right tool but a stop gap tool until we wait for golangs official 1.5 version which fixes this vendoring issue once and for all. - govendor provides consistency in terms of how import paths should be handled unlike manipulation GOPATH. This has advantages - no more compiled objects being referenced in GOPATH and build time GOPATH manging which leads to conflicts. - proper import paths referencing the exact package a project is dependent on. govendor is simple and provides the minimal necessary tooling to achieve this. For now this is the right solution.		9 years ago
..
json	Migrate to govendor to avoid limitations of godep	9 years ago
LICENSE	Migrate to govendor to avoid limitations of godep	9 years ago
README.md	Migrate to govendor to avoid limitations of godep	9 years ago
compression_selector.go	Migrate to govendor to avoid limitations of godep	9 years ago
doc.go	Migrate to govendor to avoid limitations of godep	9 years ago
encoder_selector.go	Migrate to govendor to avoid limitations of godep	9 years ago
map.go	Migrate to govendor to avoid limitations of godep	9 years ago
server.go	Migrate to govendor to avoid limitations of godep	9 years ago

README.md

rpc

gorilla/rpc is a foundation for RPC over HTTP services, providing access to the exported methods of an object through HTTP requests.

Read the full documentation here: http://www.gorillatoolkit.org/pkg/rpc