Clayton Coleman b2434de777 When connections are broken on Watch, write fewer errors to logs ...

Watch depends on long running connections, which intervening proxies
may break without the control of the remote server. Specific errors
handled are io.EOF, io.EOF wrapped by *url.Error, http connection
reset errors (caused by race conditions in golang http code), and
connection reset by peer (simply tolerated).

2014-12-18 16:15:51 -05:00

..

json

Remove unused YAML tags and GetYAML/SetYAML methods

2014-12-02 16:25:28 -08:00

doc.go

Add watch mechanism to apiserver

2014-07-18 16:47:17 -07:00

filter_test.go

Make tests pass again

2014-09-07 22:26:42 -07:00

filter.go

Make tests pass again

2014-09-07 22:26:42 -07:00

iowatcher_test.go

Make tests pass again

2014-09-07 22:26:42 -07:00

iowatcher.go

Log ErrUnexpectedEOF from watches as warnings

2014-12-05 15:03:07 -05:00

mux_test.go

Rename watch.Mux -> watch.Broadcaster

2014-12-04 00:30:51 -08:00

mux.go

Rename watch.Mux -> watch.Broadcaster

2014-12-04 00:30:51 -08:00

watch_test.go

When connections are broken on Watch, write fewer errors to logs

2014-12-18 16:15:51 -05:00

watch.go

When connections are broken on Watch, write fewer errors to logs

2014-12-18 16:15:51 -05:00