If the application is structured in such a way that messages from the other side of the client/server divide are put on channels upon arrival, which seems to be a reasonable idea, why not encapsulate the connection-handling logic in a black box exposing a (bunch of) channel(s)?
On 26 January 2014 00:01, Patrick Logan <[email protected]> wrote: > This seems like more trouble than it is worth. There are almost certainly > suitable but more established protocols and implementations for the problem > at hand. Anyway, maybe it's worth exploring. To me it seems to muddy the > waters for what core.async seems intended to provide, which seems to me to be > fairly straight-forward CSP. > > -- > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to [email protected] > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > [email protected] > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
