incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joseph Bowman <bowman.jos...@gmail.com>
Subject Re: python web framework suggestions (for Cassandra Web UI) needed
Date Fri, 09 Apr 2010 16:28:40 GMT
Lazyboy has had a lot of updates since the implementation that's in place
there. Those Digg guys have been busy. So I wouldn't use jsondra as much
more than an example of how to use tornado for the framework, rather than to
build off of as I imagine the lazyboy usage is different with current
versions. And tornado has been updated as well since, some.

On Fri, Apr 9, 2010 at 12:23 PM, Pablo Cuadrado <pablocuadrado@gmail.com>wrote:

> I like Pylons also, for what I've read. Haven't worked with it so far,
> but I'll give it try today to see how it performs.
>
> Joseph: That's great! I'm also thinking on Lazyboy, and a restful
> interface. I'll take a look at it.
>
>
>
> On Fri, Apr 9, 2010 at 1:10 PM, Joseph Bowman <bowman.joseph@gmail.com>
> wrote:
> > Way back when I wanted to try and use node.js and Cassandra, I started
> work
> > on a restful interface using Tornado and Lazyboy. I've since moved on
> from
> > that idea and the project is way out of date, but you can see what I had
> > done at this project on github - http://github.com/joerussbowman/jsondra
> >
> > On Fri, Apr 9, 2010 at 11:49 AM, Matthew Dennis <mdennis@merfer.net>
> wrote:
> >
> >> +1 for pylons, I've been quite happy with it so far - lightweight, very
> >> flexible, loosely coupled components...
> >>
> >>
> >> On Apr 9, 2010, at 10:23 AM, Gary Dusbabek <gdusbabek@gmail.com> wrote:
> >>
> >>  I like pylons.  Easy templating and relatively light weight.  In my
> >>> experience, it was easier to get something working in pylons than
> >>> django, but I am impatient.
> >>>
> >>> Gary.
> >>>
> >>>
> >>> On Fri, Apr 9, 2010 at 09:55, Pablo Cuadrado <pablocuadrado@gmail.com>
> >>> wrote:
> >>>
> >>>> Hi!
> >>>>
> >>>> I made a proposal about building a Cassandra Web UI. One of it's main
> >>>> components, will be Python on the server side.
> >>>>
> >>>> However, as Gary D. pointed out, it will be interesting to get your
> >>>> opinions on which framework to use.
> >>>>
> >>>> I suggested Django for being well-known and largely documented, but
> >>>> any other would do.
> >>>>
> >>>> As far as my experience goes on web development, this is what I -IMHO-
> >>>> think of any web framework, despite the language:
> >>>>
> >>>> - Really small footprint is a plus: "do we really need to include
> >>>> that, and that, and that other thing?"
> >>>> - Flexibility and freedom of code, another plus: "do I really need to
> >>>> inherit that class to do that"
> >>>> - Unneeded features tend to get in our way: like the "auto admin"
> >>>> panels of Django. Or the "FormAlchemy" and "SQLAlchemy" features in
> >>>> Pylons.
> >>>> - Templating features should be truly flexible, and do fast template
> >>>> parsing.
> >>>>
> >>>> Well, suggestions are needed! I would like to know your opinions on
> >>>> Django, Pylons, web2py, TurboGears, etc.
> >>>>
> >>>> Regards!
> >>>>
> >>>>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message