Well, there's almost a week since the first message in this thread! Arriving some conclusion, I think I'm going with Pylons for the UI.
Asynchronous behaviours (if needed) can be achieved with some integration with another server like Tornado. There's even some experiments of asynchronous modules in Pylons with Cogen or a WSGI asynchronous framework. Hopefully, the communication modules (between the UI and the APIs) would be encapsulated enough to be independent from the UI implementation. Thanks to all of you for your opinions! On Tue, Apr 13, 2010 at 6:28 PM, Pablo Cuadrado <pablocuadr...@gmail.com> wrote: > People: > > The "votation" is not relevant, the discussion is, and the reasons > that support each vote. And those are itself part of the research I'm > doing, and it surely will help in making the decision. > > But, they are an important part, because I didn't want to make a > decision in "solo", since this is a project relevant to any Cassandra > user. > > So, let's not discuss whether to vote or not, but expose why this or > that framework should be used. > > On Tue, Apr 13, 2010 at 5:29 PM, Eric Florenzano <flo...@gmail.com> wrote: >> On Tue, Apr 13, 2010 at 1:20 PM, Todd Lipcon <t...@cloudera.com> wrote: >>> >>> The big downside I see with Django and other WSGI based frameworks is that >>> it becomes difficult to run "background threads" in a clean way. >> >> >> This can be handled by using Eventlet or GEvent. See the gevent webchat >> demo, for example, to see how it can be done cleanly: >> http://bitbucket.org/denis/gevent/src/tip/examples/webchat/ >> >> Thanks, >> Eric Florenzano >> >
