Francis Cianfrocca
2006-May-10 08:25 UTC
[Eventmachine-talk] Something completely different
Here''s kind of a wild idea for your consideration: What if we added an application-like architecture to eventmachine, in addition to the current embedded style? So the process of creating an application would be a simple matter of dropping ruby files into particular directories, much like adding controllers to a Rails app? Something like: $ eventmachine create_application --directory my_app This would create a subdirectory framework in which you could simply drop files that implemented protocol handlers. You''d execute the application with: $ eventmachine --run --directory my_app This would allow arbitrary plugins, user-supplied logging, etc. What I ultimately would like is to get away from the whole discussion about programming languages, async events and all that, and create a much higher-level metaphor that will "just work." Sort of like how GUI programmers think not about their programs'' main loops but just about the events they need to handle. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/eventmachine-talk/attachments/20060510/2162e686/attachment.htm
Yeah, I think it is definitely worth exploring. In the end it would basically be an application generator for networking or at least event based applications? Might be nice to have generators that spit out template code depending on whether it''s a protocol, app using a protocol, gtk, cocoa etc... -Jeff Francis Cianfrocca wrote:> Here''s kind of a wild idea for your consideration: What if we added an > application-like architecture to eventmachine, in addition to the > current embedded style? So the process of creating an application would > be a simple matter of dropping ruby files into particular directories, > much like adding controllers to a Rails app? Something like: > > $ eventmachine create_application --directory my_app > > This would create a subdirectory framework in which you could simply > drop files that implemented protocol handlers. You''d execute the > application with: > > $ eventmachine --run --directory my_app > > This would allow arbitrary plugins, user-supplied logging, etc. What I > ultimately would like is to get away from the whole discussion about > programming languages, async events and all that, and create a much > higher-level metaphor that will "just work." Sort of like how GUI > programmers think not about their programs'' main loops but just about > the events they need to handle. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Eventmachine-talk mailing list > Eventmachine-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/eventmachine-talk
Francis Cianfrocca
2006-May-10 08:42 UTC
[Eventmachine-talk] Something completely different
Exactly, it would be an application generator for any kind of supported application. Once people grasp the notion of implementing protocols and timer-handlers and such-like, let''s make it possible for them to forget about everything else. On 5/10/06, Jeff Rose <rosejn at gmail.com> wrote:> > Yeah, I think it is definitely worth exploring. In the end it would > basically be an application generator for networking or at least event > based applications? Might be nice to have generators that spit out > template code depending on whether it''s a protocol, app using a > protocol, gtk, cocoa etc... > > -Jeff > > Francis Cianfrocca wrote: > > Here''s kind of a wild idea for your consideration: What if we added an > > application-like architecture to eventmachine, in addition to the > > current embedded style? So the process of creating an application would > > be a simple matter of dropping ruby files into particular directories, > > much like adding controllers to a Rails app? Something like: > > > > $ eventmachine create_application --directory my_app > > > > This would create a subdirectory framework in which you could simply > > drop files that implemented protocol handlers. You''d execute the > > application with: > > > > $ eventmachine --run --directory my_app > > > > This would allow arbitrary plugins, user-supplied logging, etc. What I > > ultimately would like is to get away from the whole discussion about > > programming languages, async events and all that, and create a much > > higher-level metaphor that will "just work." Sort of like how GUI > > programmers think not about their programs'' main loops but just about > > the events they need to handle. > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Eventmachine-talk mailing list > > Eventmachine-talk at rubyforge.org > > http://rubyforge.org/mailman/listinfo/eventmachine-talk > > _______________________________________________ > Eventmachine-talk mailing list > Eventmachine-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/eventmachine-talk >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/eventmachine-talk/attachments/20060510/047eea11/attachment-0001.htm