Check out https://github.com/halgari/com.tbaldridge.hermod for an interesting take on this.
On Wednesday, October 8, 2014 1:17:11 AM UTC-4, Sun Ning wrote: > > BTW, is there any network based core.async channel available now? > > On 10/08/2014 04:36 AM, adrian...@mail.yu.edu <javascript:> wrote: > > It's not about 'safety' (depending on what that means in this context), > but as Zach pointed out, if you aren't careful about backpressure you can > run into performance bottlenecks with unrestrained async IO operations > because although they let you code as if you could handle an unlimited > amount of connections, obviously that isn't true. There is only a finite > amount of data that can be buffered in and out of any network according to > its hardware. When you don't regulate that, your system will end up > spending an inordinate amount of time compensating for this. You don't need > to worry about this with "regular io" because the "thread per connection" > abstraction effectively bounds your activity within the acceptable physical > constraints of the server. > > On Tuesday, October 7, 2014 2:49:30 PM UTC-4, Brian Guthrie wrote: >> >> >> On Mon, Oct 6, 2014 at 12:10 AM, <adrian...@mail.yu.edu> wrote: >> >>> Zach makes an excellent point; I've used AsyncSocketChannels and its irk >>> ( >>> http://docs.oracle.com/javase/8/docs/api/java/nio/channels/AsynchronousServerSocketChannel.html), >>> >>> with core.async in the past. Perhaps replacing your direct java.net.Sockets >>> with nio classes that can be given CompletionHandlers ( >>> http://docs.oracle.com/javase/7/docs/api/java/nio/channels/CompletionHandler.html) >>> >>> would be a better fit. >>> >> >> Once I do some performance instrumentation I'll give that a shot. I admit >> that I'm not familiar with all the implications of using the nio classes; >> were I to switch, is it safe to continue using go blocks, or is it worth >> explicitly allocating a single thread per socket? >> >> Brian >> > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clo...@googlegroups.com <javascript:> > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+u...@googlegroups.com <javascript:> > 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+u...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- 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.
