Hi. The ADS position is simple:
* We are not in favor of Tornado because we feel that loosing the main selling point (asynchronous) of Tornado by using it in a WSGI environment is a point against it. * We tested Flask more thoroughly than Pyramid but developed a preference for the clean and simple model of Flask. Also the additions to Flask (especially grouping the URLs) that people mentioned make it a strong contender. Benoit. On Thu, Oct 6, 2011 at 9:47 AM, Peter J. Halliday <[email protected]> wrote: > My comment was meant in response to this thread and not where it was > responded before. We'd rather not wait that long either. There are several > things that are interesting about Tornado. Including the ability to combine > WSGI Apps within Tornado. But I think they'll be more support, and more > apps people are developing of us to use. > ------------------------------------------ > Peter Halliday > Cornell University Library IT > Repositories Group > [email protected] > (Phone:) 607-255-1790 > (Cell:) 607-329-6905 > > > > > > > On Oct 5, 2011, at 6:05 PM, Joe Blaylock wrote: > > CERN hackers, please comment on in case my summary diverged someplace. > > Cornell/Harvard/SLAC hackers, please join in with your preferences and > > findings, to see whether we converge. We can make another telecon > > tomorrow at 16:30 in order to discuss the findings interactively and in > > more detail, if needed. > > Anyone, if you have not joined in the discussion yet, and if you have > > another suggestion to make, please holler! > > I'm fine with either, but would like to go faster, so have a mild > preference for flask/werkzeug/jinja2. > > Joe > > > -- Benoit Thiell The SAO/NASA Astrophysics Data System http://adswww.harvard.edu/
