Taking Celluloid out is easier than taking faye/eventmachine. One approach could be to do as in activejob, i.e. leave the interface and a dev-only implementation in Rails and let other gems to the heavy work.
This would greatly improve the choices, as eventmachine is not the only event-based WS server around (I think reel has done something for celluloid-io, for example). quarta-feira, 6 de Janeiro de 2016 às 00:55:22 UTC+1, Mike Perham escreveu: > > I've noticed that Rails's gem dependency count has gone from 34 in 4.2.4 > to 55 in 5.0.beta1. I think much of this is due to pulling in all of > Celluloid and EventMachine via ActionCable. I'd be interesting in working > to minimize this footprint, perhaps by using concurrent-ruby's thread pools > rather than celluloid actors. > > Is there any interest in me pursuing this work? Has anyone else > investigated in this direction? > > Mike > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
