go-omaha/omaha
Michael Marineau 9a796427d5 omaha: distinguish zero and unset in ping active days field
Unlike the other fields unset here would mean unknown rather than "0" so
we must distinguish between the two. In the end it isn't very
significant since our update server and none of our clients use these
self-reported active times, exclusively using when pings were received.
2017-04-24 13:05:53 -07:00
..
codes.go omaha: support using status codes as error values 2017-04-21 14:12:44 -07:00
handler.go omaha: add complete http handler implementation 2017-04-21 14:12:44 -07:00
handler_test.go omaha: add complete http handler implementation 2017-04-21 14:12:44 -07:00
isclosed.go omaha: implement server based on OmahaHandler 2017-04-21 14:12:44 -07:00
package.go omaha: add helper method for computing package metadata 2017-04-21 14:12:44 -07:00
package_test.go omaha: add helper method for computing package metadata 2017-04-21 14:12:44 -07:00
protocol.go omaha: distinguish zero and unset in ping active days field 2017-04-24 13:05:53 -07:00
protocol_test.go omaha: remove lingering references to mantle 2017-04-24 12:23:53 -07:00
server.go omaha: implement server based on OmahaHandler 2017-04-21 14:12:44 -07:00
server_test.go omaha: implement server based on OmahaHandler 2017-04-21 14:12:44 -07:00
system.go omaha: rework/cleanup protocol APIs 2017-04-21 14:12:44 -07:00
trivial_server.go omaha: add basic but functional omaha server for testing 2017-04-21 14:12:44 -07:00
trivial_server_test.go omaha: add basic but functional omaha server for testing 2017-04-21 14:12:44 -07:00
update.go omaha: add complete http handler implementation 2017-04-21 14:12:44 -07:00
update_test.go omaha: add structure for representing a single app update 2017-04-21 14:12:44 -07:00