Jonathan, Improving resilience is about making the application better prepared for every day events. The brainstorming is supposed to bring to light more such events that users get confronted with.
In my opinion the current algorithms don't account for events that are unavoidable such as: - Executors dropping off the map while running a thread. - Managers having network problems and not being able to accept the Executor's response - Applications temporarily loosing connection to the Manager - Add here your own I have nothing against any kind of discussing as it keeps the ideas flowing and can't be bad. Tibor > -----Original Message----- > From: Jonathan Mitchem [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 14, 2006 1:21 PM > To: Tibor Biro > Cc: [email protected] > Subject: Re: [Alchemi-developers] Improving Alchemi resilience > > I hadn't replied to this earlier, and meant to. > > I don't know if throwing new implementations of ideas at things is > really the best idea. True, there are things we can add to make > things more resilient, but right now I think the most important goal > is actually quantifying an answer to the question "why isn't the > current implementation resilient?" > > Once we have that, we can brainstorm solutions to "fix" it, and then > implement them. > > Of course, I don't mean to say that brainstorming for new ideas right > now is a bad thing. > > Jonathan ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Alchemi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alchemi-developers
