Howard M. Lewis Ship

Feels like there needs to be a bit more documentation about streaming responses, overlapping with core.async.

I'm learning about and reviewing metric support in Pedestal, with an eye towards opentracing -> opentelemetry and these notes about Micrometer. What's changed since 2018 in this space?

This is starting to feel like something that will slip to 0.5.12 then. I have not yet looked at the Pedestal2 code base.

I'm sure Pedestal2 is nice, but we're focused on maintaining backwards compatibility and that adds a lot of challenge here, and possibly some duplication if we go on a path...

Ended up embracing Open Telemetry (see #804).

At time plus 7 years ... I'm afraid we're going to close this. I agree w/ Paul that a better pattern is an error handling interceptor and a functionality (enter...

As implemented in 0.7.x, an endpoint map can define several callbacks (on-open, on-close, on-error, on-text, and on-binary). The first three are passed the jakarta.websocket.Session. With some work, I could pass...

I was just reviewing earlier web socket changes. In 0.7.x, you can provide callbacks related to web socket connections, which are bundled up with a path and passed to io.pedestal.websocket/add-endpoints....

I think the enhancements in 0.7.0 already address this issue. I'm going to close this issue unless. Please re-open if you have further clarifications.

Please re-open if you can put together a reproducible test case. You may also find that enabling debugging output for the io.pedestal.interceptor.chain namespace will be enlightening about what Pedestal is...