go-omaha/omaha/client
Michael Marineau d946c1e7b2 client: disable checking for ping and event status in responses
Turns out CoreUpdate does not currently send <ping status="ok"> and
<event status="ok"> in responses like the protocol says it should.
2017-06-09 18:40:25 -07:00
..
client.go client: disable checking for ping and event status in responses 2017-06-09 18:40:25 -07:00
client_test.go client: support sending events asynchronously 2017-06-09 18:40:25 -07:00
error.go client: send error events if update check or ping fails 2017-06-09 18:40:25 -07:00
error_test.go client: implement exponential backoff on temporary network errors 2017-06-02 18:44:29 -07:00
example_test.go client: add rough example for using the client 2017-06-05 13:23:32 -07:00
fuzzytime.go client: add fuzzy timer 2017-06-02 18:42:53 -07:00
fuzzytime_test.go client: add fuzzy timer 2017-06-02 18:42:53 -07:00
http.go client: send error events if update check or ping fails 2017-06-09 18:40:25 -07:00
http_test.go client: report sensible errors if response is excessively large or empty 2017-05-25 13:13:09 -07:00
machine_linux.go client: define default version as a constant 2017-06-02 18:44:29 -07:00
machine_linux_test.go client: add support for machine-wide omaha clients 2017-05-25 13:57:28 -07:00
update_engine_events.go client: define error codes and events used by update_engine 2017-06-09 18:40:25 -07:00