Go to file
Michael Marineau 75a1125f53 omaha: split request and response structures
Despite having common names between the request and response XML
structures the actual values which may appear in them are completely
disjoint. Splitting the types up makes the protocol easier to understand
when reading the code. When applicable, required fields like status are
passed to Add* methods.
2017-04-21 14:12:44 -07:00
fixtures feat(omaha): add a machineid field 2014-03-17 14:29:04 -07:00
omaha omaha: split request and response structures 2017-04-21 14:12:44 -07:00
.gitignore Initial commit 2013-03-27 16:59:16 -07:00
.travis.yml travis.yml: try to build all of the packages 2013-06-25 08:56:17 -07:00
LICENSE LICENSE: Initial commit 2013-06-23 19:42:30 -07:00
README.md Update README.md link to github.com/google/omaha 2015-11-01 08:48:27 +00:00

README.md

Go Omaha

Implementation of the omaha protocol in Go.

https://github.com/google/omaha

Docs

http://godoc.org/github.com/coreos/go-omaha/omaha

Build Status