tomer doron

> JSON over UDP sounds like a fun challenge for me. I haven't set up a channel pipeline yet, but this sounds like a good first time. @fabianfett we done...

I think this can be potentially achieved with the current API. check out the [following test](https://github.com/swift-server/swift-service-launcher/blob/master/Tests/ServiceLauncherTests/LifecycleTests.swift#L519) ``` func testExternalState() { enum State: Equatable { case idle case started(String) case shutdown...

cc @yim-lee @ktoso @ddossot

@weissi @ddossot the original design thinking here was that state would be contained within each `LifecycleItem`. so, to @weissi's example if some unit of logic uses swift-nio and needs to...

thanks @ktoso for the additional input. > Long story short: the var state = State.idle is terrifying (for concurrency reasons) and something I really really would want to not teach...

> Based on previous experiences I think it's sufficient to keep any associated state/data within the individual LifecycleItems themselves--by this I am not suggesting we move the proposed feature from...

@weissi did you notice the new `registerStateful` methods? they allow start to return a state which is then handed off to the corresponding shutdown. this solves at least some of...

@weissi I see. in most cases that need something like this, I saw at the "shared" instance created outside the lifecycle and the "starting" of it done in the start...

+1

thanks for reporting @mufumade, would you like to make a PR to address this?