Folks, if anyone wants to submit a SOC project, you have to get on the stick and do it now, as the deadline is Saturday. Note here that the RubyCentral folks flagged EM as a good source for ideas: http://www.rubycentral.org/projects/soc2007/ideas/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/eventmachine-talk/attachments/20070321/8b729682/attachment.html
On 3/21/07, Francis Cianfrocca <garbagecat10 at gmail.com> wrote:> Folks, if anyone wants to submit a SOC project, you have to get on the stick > and do it now, as the deadline is Saturday. Note here that the RubyCentral > folks flagged EM as a good source for ideas: > http://www.rubycentral.org/projects/soc2007/ideas/ >Francis, What exactly they mean, when they say make it run on top of drb and how exactly its going to make things faster? As i asked earlier, it would be nice if for REALLY long running taks, which can potentially block event loop, it would be good if eventmachine can support a process based architecture out of box. Delegating tasks to background processes and setting up callbacks and stuff. Load based auto spawning of processes would be also nice. But above are just ideas, If any student can pick up and work on them, it would be awesome. technically i am disqualified to participate. -- gnufied ----------- There was only one Road; that it was like a great river: its springs were at every doorstep, and every path was its tributary. http://people.inxsasia.com/~hemant
On 3/21/07, hemant <gethemant at gmail.com> wrote:> On 3/21/07, Francis Cianfrocca <garbagecat10 at gmail.com> wrote: > > Folks, if anyone wants to submit a SOC project, you have to get on the stick > > and do it now, as the deadline is Saturday. Note here that the RubyCentral > > folks flagged EM as a good source for ideas: > > http://www.rubycentral.org/projects/soc2007/ideas/ > > > > Francis, What exactly they mean, when they say make it run on top of > drb and how exactly its going to make things faster? > > As i asked earlier, it would be nice if for REALLY long running taks, > which can potentially block event loop, it would be good if > eventmachine can support a process based architecture out of box. > Delegating tasks to background processes and setting up callbacks and > stuff. > > Load based auto spawning of processes would be also nice. > > But above are just ideas, If any student can pick up and work on them, > it would be awesome. technically i am disqualified to participate. >I have a amateur kinda implementation, which handles jobs based on process based archs. its really simple, because it piggybacks on drb.
On 3/21/07, hemant <gethemant at gmail.com> wrote:> > > Francis, What exactly they mean, when they say make it run on top of > > drb and how exactly its going to make things faster? > >Hemant, are you thinking about an architecture in which a central "broker" process would distribute service requests across a set of processes? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/eventmachine-talk/attachments/20070321/1e70c982/attachment.html
On 3/21/07, Francis Cianfrocca <garbagecat10 at gmail.com> wrote:> On 3/21/07, hemant <gethemant at gmail.com> wrote: > > > Francis, What exactly they mean, when they say make it run on top of > > > drb and how exactly its going to make things faster? > > > > > > > Hemant, are you thinking about an architecture in which a central "broker" > process would distribute service requests across a set of processes? >Yes something like that. Currently I have a central process, which runs a event loop and all the child processes also run event loops, and a lifeline is maintained between child and parent using drb. its coming along nicely and works for time consuming jobs. PS: Sorry for late reply. I was in hibernation. --