Great timing on the new blog post. I'm ramping up on my first "real" clojure app, and have been planning to use Component for this piece. I read the first blog post yesterday and it sounded interesting, but I've pretty much locked down the stack I'm going to use (you can evaluate libraries forever, but at some point you just have to stop looking and pick one to go with).
But after reading the new post, I think it's worth taking a look at Trapperkeeper. Even if I don't switch now, if all goes well I would like to turn this app into a larger SaS offering, possibly multi-tenant, and I could see something like Trapperkeeper helping there. I get the distinct impression you have some former OSGI users on your team? This reminds me a lot of the service registry in OSGI. And I don't mean that as an insult - the service registry was the best part, it was all the other crap that made it painful to use (particularly anything from eclipse, which ruined OSGI in my opinion, but that's another rant). Anyway, this looks like something that could be useful in many cases, and thank you for open-sourcing it. -- 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/d/optout.
