Find a file
Matthew Holt 402f423693 Implement "global" state for modules, OnLoad and OnUnload callbacks
Tested for memory leaks and performance. Obviously the added locking and
global state is not awesome, but the alternative is a little uglier IMO:
we'd have to make some sort of "liaison" value which stores the state,
then pass it around to every module, and so LoadModule becomes a lot
less accessible, and each module would need to maintain a reference to
it... nope, just ugly. I think this is the cleaner solution: just make
sure only one Start() happens at a time, and keep global things global.

Very simple log middleware is an example.

Might need to reorder the operations in Start() and handle errors
differently, etc. Otherwise, I'm mostly happy with this solution...
2019-04-08 00:00:14 -06:00
cmd/caddy2 Very basic middleware and route matching functionality 2019-03-31 20:41:29 -06:00
modules/caddyhttp Implement "global" state for modules, OnLoad and OnUnload callbacks 2019-04-08 00:00:14 -06:00
.gitignore Fix goroutine leak in Run 2019-03-27 12:36:30 -06:00
admin.go Fix goroutine leak in Run 2019-03-27 12:36:30 -06:00
admin_test.go Performance testing Load function 2019-03-26 19:42:52 -06:00
caddy.go Implement "global" state for modules, OnLoad and OnUnload callbacks 2019-04-08 00:00:14 -06:00
listeners.go Close listeners which are no longer used 2019-04-02 15:31:02 -06:00
modules.go Implement "global" state for modules, OnLoad and OnUnload callbacks 2019-04-08 00:00:14 -06:00
modules_test.go Initial commit 2019-03-26 12:00:54 -06:00