Soam Vasani 3d5e52dc3d Router integration with poolmgr and controller ...

Router uses poolmgr to specialize pods when necessary.

Router uses controller to get the list of triggers to listen for.  For
now this integration is pretty crappy -- we just poll the controller
every few seconds and cache the result.  The right way would be to
have some sort of watch API on the controller and use that.  Or maybe
share access to etcd directly.

2016-11-01 18:22:04 -07:00

..

functionHandler_test.go

Define main resource types

2016-09-10 00:59:39 -07:00

functionHandler.go

Router integration with poolmgr and controller

2016-11-01 18:22:04 -07:00

functionServiceMap_test.go

Define main resource types

2016-09-10 00:59:39 -07:00

functionServiceMap.go

Define main resource types

2016-09-10 00:59:39 -07:00

httpTriggers.go

Router integration with poolmgr and controller

2016-11-01 18:22:04 -07:00

mutablemux_test.go

Move packages to root dir from src/

2016-09-07 14:07:26 -07:00

mutablemux.go

Router integration with poolmgr and controller

2016-11-01 18:22:04 -07:00

router_test.go

Router integration with poolmgr and controller

2016-11-01 18:22:04 -07:00

router.go

Router integration with poolmgr and controller

2016-11-01 18:22:04 -07:00

util_test.go

Move packages to root dir from src/

2016-09-07 14:07:26 -07:00