On Sun, Nov 9, 2008 at 2:27 AM, adrian <[EMAIL PROTECTED]> wrote:
> Not a helpful comment.If what you said were true, why is there an
> AppEngine Helper for Django?
> Obviously there are some issues.
There's an App Engine helper for django because it's not easy to
transplant django from usin
On Sat, Nov 8, 2008 at 1:27 PM, adrian wrote:
> Not a helpful comment.If what you said were true, why is there an
> AppEngine Helper for Django?
> Obviously there are some issues.
you'll have some issues using a django app as it is because it
initializes stuff that won't work inside app engin
You should look at the django documentation and check out the forms
libraries. I believe those work normally under app engine. The
gotcha is that the forms library changed between django versions .96
and 1.0, so you'll need to decide which version to use, which is a
whole 'nother question that
Not a helpful comment.If what you said were true, why is there an
AppEngine Helper for Django?
Obviously there are some issues.
> Django is not App Engine-specific.
>
> Dave.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
On Fri, Nov 7, 2008 at 9:35 PM, adrian <[EMAIL PROTECTED]> wrote:
> I will learn about those, thanks.
>
> But there's still an AppEngine-specific version of the question:
> does Django as supported on AppEngine have any useful validation
> features, or are they in
> the part of Django that is not
I will learn about those, thanks.
But there's still an AppEngine-specific version of the question:
does Django as supported on AppEngine have any useful validation
features, or are they in
the part of Django that is not supported? Anyone got examples that
prevent attacks?
I validated most thin
This question is not app engine specific. Users can request a GET or
POST with whatever values they want regardless of the underlying
technology. You should google "Cross Site Scripting" and "SQL
Injection" to learn about the various evil things users can do to you
if you don't validate your inp