This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-24
Channels
- # adventofcode (4)
- # announcements (1)
- # aws (6)
- # babashka (18)
- # babashka-sci-dev (18)
- # beginners (12)
- # calva (43)
- # circleci (3)
- # clj-kondo (96)
- # cljdoc (2)
- # clojure (89)
- # clojure-australia (2)
- # clojure-europe (26)
- # clojure-nl (3)
- # clojure-norway (11)
- # clojure-spec (8)
- # clojure-uk (1)
- # clojurescript (28)
- # cursive (25)
- # datahike (6)
- # datalevin (56)
- # datomic (12)
- # docker (15)
- # emacs (9)
- # events (2)
- # figwheel (3)
- # fulcro (15)
- # gratitude (10)
- # introduce-yourself (8)
- # lsp (16)
- # malli (6)
- # nbb (2)
- # off-topic (23)
- # other-languages (2)
- # pathom (4)
- # portal (25)
- # practicalli (1)
- # re-frame (9)
- # releases (1)
- # shadow-cljs (8)
- # sql (6)
- # timbre (3)
Thanks to @quoll for making me understand graph databases and datalog! A couple of days ago I clicked https://github.com/quoll/asami/wiki in the https://github.com/quoll/asami and to my very pleasant surprise found a dense and at the same time accessible documentation of asami, graph db's and datalog in general. Great work, greatly appreciated :heart_hands: š
9I salute the person who invented/discovered the interceptor pattern (cfr Pedestal, Sieppari, Papillon and others), why did I discover this only after 20 years into my career? It's like a fundamental particle āļø of software engineering, right?
8I'm actually unfamiliar with it, so thanks for the tip! š
I found these videos useful. There's also the #interceptors channel. ā¢ https://youtu.be/bDN898hu_wQ ā¢ https://youtu.be/_Cf-STRvFy8
1@U052A8RUT You beat me to it. š I'm 15min in the Proctor video, and can attest it's very understandable 
Thanks for posting your original gratitude post.
Interceptors are at least twenty years old, though I can't tell who originated it. It's probable the pattern is even older than that under different names (e.g., audio/video processing pipelines). The first printed reference I can find for the interceptor is from _<https://en.wikipedia.org/wiki/Pattern-Oriented_Software_Architecture#POSA2|Pattern-Oriented Software Architecture, 2nd Ed>._ from 2000. (Ed. 1 doesn't list the pattern.) The POSA2 book pattern is quite general. The first reference I can find to it being used for _web_ requests is the "intercepting filter". Here's a <https://web.archive.org/web/20021001190923/http://java.sun.com/blueprints/corej2eepatterns/Patterns/InterceptingFilter.html|Sun page> on the topic from 2002.
@U10EC98F5 I skimmed the link you referenced, but at least two considerations appear absent. 1) That the executor handles asynchronous filters protecting other filters from the mess that is asynchronous nesting. 2) That the interceptor filters queued and stack run are available for manipulation on the context itself! No doubt that the lineage of the Interceptor pattern derives from this prior art, but in my mind it deserves a 2.0 status with these criteria met. Begs the question how old 2.0 is?
@U03B2SRNYTY Not sure which link you're referring to, but the Sun page on the InterceptingFilter talks about dynamically altering the interceptor list. I think that meets your criterium #2 iiuc. I know for sure that Netty's ChannelPipeline meets both criteria, and it dates back to 2008, predating Pedestal by 5 years. Netty itself dates back to 2004, so it's possible interceptors existed even earlier in a different file. (And I'm not even sure that's the oldest async usage. E.g., Tomcat has interceptors and was started back in 1998, but I'm not very familiar with it)
@U10EC98F5 Thanks! I did say I skimmed it. š Much obliged that you confirmed that #2 is met.