This is simple brilliant... The approach proposed and the component "framework" implementing it finally solves the issue with the "necessary evil" (start/stop interactions with statefull components in any bigger Clojure app) by cleverly taking only the best ideas (like using inferred dependency graph to automatically start/stop components in the correct order) from Java DI frameworks like Spring, which i have a lot of experience with. Thank you very much for this work.
Dňa štvrtok, 21. novembra 2013 3:01:19 UTC+1 Stuart Sierra napísal(-a): > > This is a small library/framework I've been working on for a few months. > > https://github.com/stuartsierra/component > > I use this to manage runtime state in combination with my "reloaded" > workflow using tools.namespace.[1] > > I've started using this on some personal and professional projects and it > seems to be working fairly well. > > > [1]: http://thinkrelevance.com/blog/2013/06/04/clojure-workflow-reloaded > > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
