Hi Robin, You can absolutely specify an executor of :none if you're sure you won't be doing any blocking in your request handler. If everything's wrapped by a go-block, that's certainly the case, and is probably the most efficient approach. However, Aleph just needs some java.util.concurrent.Executor, so using the core.async executor is also a valid approach.
By the way, I'm more likely to notice these sorts of questions if you ask them on the Aleph mailing list: https://groups.google.com/forum/#!forum/aleph-lib Zach On Tuesday, February 17, 2015 at 1:35:53 AM UTC-8, Robin Heggelund Hansen wrote: > > From what I can see, aleph allows me to set a executor to handle client > requests. I'm already using core.async pretty heavily. Is there any reason > why I shouldn't pass core.async's executor to aleph? I see I can also make > every client request start on aleph's dispatch thread. Considering > absolutely every request spawns a go-block, might it even be a good idea to > not run aleph with an executor at all? > > Thanks! > -- 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.
