I did something similar for a database connection component, that could connect
to multiple databases at runtime and had to maintain internal state. I didn’t
need to make the individual connections components, but this was because the DB
driver handles state internally.
In my case I used an
Thanks for your replies.
I've looked at clj-headlights a bunch, and datasplash, too. I was mistaken
to think that AOT was necessary. Earlier in the project, AOT simplified a
few things, like affording the use of anonymous functions (in ParDo
implementations), and I don't think I realized
We don't want such a tiny library to pull in any other dependencies. The
subset of ASM used by defexception is so core and so minimal that we think
it's extremely unlikely to ever break. A dependency collision with an ASM
used by another library seems far more likely.
On Saturday, August 24,
Hello,
I'm writing an app/system that subscribes to a number of feeds, the number
and configuration of the feeds is a configurable run-time thing.
Seems like I should have a Feed component, which is passed its config when
instantiated.
But having a named slot in the system for each feed would
