webapp, tipfy或django在谷歌app引擎上

which one are you using on google app engine?

你在谷歌应用引擎上使用的是哪一个?

what were the reasons behind your decision?

你做决定的原因是什么?

6 个解决方案

#1

Tipfy

It's developed as an extension to webapp, so it's just one abstracted layer.
它是作为webapp的扩展而开发的，所以它只是一个抽象层。
That abstracted layer is very minimal. Methods have the same or similar names to their webapp counterparts, but with useful extras that you'd probably end up coding yourself.
抽象层非常小。方法与webapp中的方法有相同或相似的名称，但是有一些有用的附加功能，你可能会自己编写代码。
Simple routing; if you're familiar with Django or web2py, tipfy's routing is a huge step forward.
简单的路由;如果您熟悉Django或web2py, tipfy的路由是一个巨大的进步。

Finally, tipfy has an excellent support community. Rodrigo Moraes is especially helpful and engaging. Questions are answered very quickly, and courteously.

最后，tipfy拥有一个优秀的支持社区。罗德里戈·莫雷斯尤其乐于助人和吸引人。回答问题的速度很快，而且很有礼貌。

#2

Although I mainly work with Django for larger work related projects (hosted elsewhere) I've tended to use webapp for things on App Engine. App Engine to me is best suited for small webservices that you then link together into a full app, and webapp suits that usecase pretty well. Small hacks as well I always use webapp just for simplicity and speed of development. Examples imified-demo.appspot.com, gitbug.appspot.com and github.com/garethr/appengine-image-host

虽然我主要与Django合作进行大型工作相关的项目(托管在其他地方)，但我倾向于在应用引擎上使用webapp。对我来说，应用程序引擎最适合小型的web服务，然后将它们链接到一个完整的应用程序中，而webapp非常适合usecase。我也经常使用webapp来简化和提高开发速度。示例imified-demo.appspot.com、gitbug.appspot.com和github.com/garethr/appengine-image-host

Downside is tool support, you probably have to hack together little things to make your life easier that already exist in the Django world (eg. a test runner http://github.com/garethr/appengine-testrunner)

缺点是工具支持，您可能需要将一些小的东西组合在一起，以使您的生活更轻松，而这些东西在Django世界中已经存在(例如)。一个测试运行器http://github.com/garethr/appengine-testrunner)

Anecdotal evidence from a previous project made me feel like Django was a little slow on App Engine for my liking.

之前一个项目的一些趣闻让我觉得Django在我喜欢的应用程序引擎上有点慢。

Tipfy sounds a good idea, hopefully a case of App Engine maturing as a platform, although I have no personal experience with it at this stage.

Tipfy听起来是个不错的主意，希望它能成为一个成熟的应用程序引擎平台，尽管我在这个阶段没有个人经验。

All things considered it depends. A big project with multiple developers should probably opt for Django. It's standard ways of doing things will make life easier for everyone. For one off projects I personally prefer webapp or similar. But set aside some time for building your own tools as well as writing your application.

一切都视情况而定。拥有多个开发人员的大型项目可能会选择Django。这是做事情的标准方式，会让每个人的生活更轻松。我个人更喜欢webapp或者类似的项目。但是要留出一些时间来构建自己的工具和编写应用程序。

#3

Imho..

Imho . .

Django - the only part that's relevant is the templating and maybe the no rel..

Django—唯一相关的部分是模板，也许是no rel.

Webapp - never tried it after

Webapp——以后再也没试过

Tipfy - is what I'm using, seems to be more "pylons" like, has a basic apps/modules structure and lots of "helpers" which quite frankly should be in the google.appengine.api Easy to implement templates and routing is nice. Your pretty much left on your own on how to use tipfy and how to structure the application.

我用的是Tipfy，看起来更像“pylons”，它有一个基本的应用程序/模块结构和很多“助手”，坦白地说应该在google.appengine中。易于实现模板和路由的api很好。关于如何使用tipfy和如何构造应用程序，您几乎完全可以自行决定。

#4

I'm still investigating, but I think webapp and tipfy will be a lighter framework than django. Right now, I am using just webapp and the cold start times are already too long. I want to use tipfy for sessions and keep everything else in webapp.

我仍在调查，但我认为webapp和tipfy将比django更轻。现在，我用的是webapp，冷启动时间已经太长了。我想在会话中使用tipfy，并在webapp中保存所有其他内容。

What are you trying to optimize for? Speed of development? Easy of programming? Obscure middleware?

你想优化什么?速度的发展吗?简单的编程?模糊的中间件?

#5

I would still prefer Django for its structure and a high support available over internet for it and for the following reasons:

我仍然倾向于Django的结构，并在互联网上提供高支持，原因如下:

Webapp offcourse is light weight, but Django comes with a nice structure which saves a lots of time while working on a large application.
Webapp offcourse是轻量级的，但是Django提供了一个很好的结构，在处理大型应用程序时可以节省很多时间。
Google app engine does provide a good document for working with Webapp but Django has a large community of programmers and thus proves to be a better choice for implementing some complex applications.
谷歌应用程序引擎确实为Webapp提供了很好的文档，但是Django拥有大量的程序员社区，因此被证明是实现一些复杂应用程序的更好选择。
Django provides a default admin panel, which otherwise would need to be created in Webapp, though Google app provides an admin interface but that is not equivalent of a full fledged customizable admin panel.
Django提供了一个默认的管理面板，否则就需要在Webapp中创建这个面板，尽管谷歌应用程序提供了一个管理界面，但这并不等同于一个完整的可定制的管理面板。
Webapp itself follows Django for its templates.
Webapp自身的模板遵循Django。

#6

I use webapp2 which is a derivative of tipfy (in fact the functions and docs are in many cases identical) and takes ideas from other frameworks too. I recommend taking a look at some boilerplates if you are starting a new project and want to get a quick feel for the framework. Take a look at this boilerplate i've been working on with coto if you are interested in webapp2: http://github.com/coto/gae-boilerplate

我使用webapp2，它是tipfy的一个衍生版本(实际上函数和文档在很多情况下是相同的)，并且从其他框架中获取想法。如果您正在启动一个新项目，并希望快速了解框架，我建议您查看一些样板文件。如果您对webapp2 (http://github.com/coto/gae-boilerplate)感兴趣，请查看我与coto合作的这个样板文件

#1