registry/notifications
Noah Treuhaft ad6bb66faf Add notification filtering by target media type
The Hub registry generates a large volume of notifications, many of
which are uninteresting based on target media type.  Discarding them
within the notification endpoint consumes considerable resources that
could be saved by discarding them within the registry.  To that end,
this change adds registry configuration options to restrict the
notifications sent to an endpoint based on target media type.

Signed-off-by: Noah Treuhaft <noah.treuhaft@docker.com>
2016-09-16 12:01:03 -07:00
..
bridge.go Propogate tag as a functional argument into the notification system to attach 2016-03-23 14:57:52 -07:00
bridge_test.go Merge pull request #1522 from RichardScothern/tag-events 2016-03-23 16:41:29 -07:00
endpoint.go Add notification filtering by target media type 2016-09-16 12:01:03 -07:00
event.go Propogate tag as a functional argument into the notification system to attach 2016-03-23 14:57:52 -07:00
event_test.go Fix content type for schema1 signed manifests 2016-01-18 16:08:02 -08:00
http.go Add transport field to EndpointConfig struct 2016-07-11 11:52:23 -07:00
http_test.go Add transport field to EndpointConfig struct 2016-07-11 11:52:23 -07:00
listener.go manifestServiceListener.Get to pass down options parameter 2016-09-01 18:50:56 -06:00
listener_test.go Remove signature store from registry. Return a generated signature for manifest 2016-05-27 13:19:26 -07:00
metrics.go Typo fixes in comments 2016-02-10 16:26:29 -08:00
sinks.go Add notification filtering by target media type 2016-09-16 12:01:03 -07:00
sinks_test.go Add notification filtering by target media type 2016-09-16 12:01:03 -07:00