pedestal

hlship 2025-03-08T01:10:27.055159Z

More progress today but it took a lot of debugging to get right. The new io.pedestal.service.websocket namespace will work identically whether you are using Jetty or Http-Kit. There were a lot of challenges to get three fundamentally different lifecycles to align with each other (the lifecycles of the web socket connection itself - when various callbacks get invoked, when the FnEndpoint class gets instantiated, and so forth).

2
❤️ 1
🩻 1
2025-03-08T21:52:26.712179Z

Hi, I was reading pedestal sources when I came across this function https://github.com/pedestal/pedestal/blob/master/interceptor/src/io/pedestal/interceptor.clj#L58 Line 68, in the case the response isn't a core.async channel, the response is computed a second time if I am not mistaken. Shouldn't the code just be (assoc context :response response) ? I can open an issue if needed. Cheers!

hlship 2025-03-08T22:39:10.481709Z

Great catch … it of course passed all tests despite being broken.

hlship 2025-03-08T22:39:24.814849Z

I’ll fix it in my current PR.

2025-03-08T22:40:14.261629Z

NP I am glad I was randomly looking at it!

hlship 2025-03-08T23:19:07.876879Z

It’s a challenge when there’s no-one to review PRs.

hlship 2025-03-08T23:20:08.388669Z

Test only go so far, and you get blind to your own code, especially when I’m fitting in Pedestal work around other things I’m up to. So thanks again!

2025-03-09T01:14:45.652629Z

I get it you're welcome, It seems like you have been doing a quite a lot to push pedestal forward! Thanks!