Like Joe said we would definitely want to make a decision and get going on the work needed to get it done.
If anyone wants to chat with the developers they hang out in IRC on freenode at #pocoo. Peter Sent from my iPhone On Oct 5, 2011, at 6:49 PM, "Samuele Kaplun" <[email protected]> wrote: > Il giorno mer, 05/10/2011 alle 23.20 +0200, Tibor Simko ha scritto: >> I'd therefore tentatively summarise our position by saying that >> Flask/Werkzeug/Jinja seems to be our clear favourite. (But also that it >> would be very interesting to spend 3-4 weeks or so in order fully >> explore pros/cons/lockup-dangers/migration-work associated with >> switching to Tornado's paradigm for our concrete application, including >> building simplified prototype to re-measure search citation dictionary >> setup scalability, and stuff.) > > Meanwhile, while studying Flask features: > > * <http://flask.pocoo.org/docs/patterns/streaming/> is ready to help us > reimplementing req.write() feeling of perform_request_search :-) > * <http://flask.pocoo.org/docs/patterns/wtforms/> is ready to help us > reimplementing websubmit :-) > * > <http://flask.pocoo.org/docs/patterns/lazyloading/#converting-to-centralized-url-map> > is ready to help arXiv :-) > * <http://flask.pocoo.org/docs/patterns/packages/#larger-applications> > is ready to help us reimplementing WebInterfaceDirectory > > etc. Great! > > Cheers, > Sam > > -- > Samuele Kaplun > Invenio Developer ** <http://invenio-software.org/> >
