2007/12/3, Malcolm Tredinnick <[EMAIL PROTECTED]>:
> On Mon, 2007-12-03 at 13:09 -0800, David Cramer wrote:
> > For the most part I'm just doing if request.POST to validate.
>
> This isn't completely sufficient because it's possible to submit a form
> via POST with no data (e.g. a form with checkb
On Mon, 2007-12-03 at 13:09 -0800, David Cramer wrote:
> For the most part I'm just doing if request.POST to validate.
This isn't completely sufficient because it's possible to submit a form
via POST with no data (e.g. a form with checkboxes and maybe some fields
that aren't filled in). That's w
On 12/3/07, David Cramer <[EMAIL PROTECTED]> wrote:
> For the most part I'm just doing if request.POST to validate.
The request.method attribute exists precisely for this purpose, so
that you can find out what the HTTP request method was ;)
--
"Bureaucrat Conrad, you are technically correct --
For the most part I'm just doing if request.POST to validate.
On Dec 3, 11:16 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2007-12-03 at 11:00 -0800, David Cramer wrote:
> > Just my 2 cents...
>
> > If you drop request.POST, request.GET, and replace them all with
> > request.DATA -
On Mon, 2007-12-03 at 11:00 -0800, David Cramer wrote:
> Just my 2 cents...
>
> If you drop request.POST, request.GET, and replace them all with
> request.DATA -- we're going to again be branching away from Django
> trunk.
>
> For our uses -- POST and GET are completely different things --
> wh
Just my 2 cents...
If you drop request.POST, request.GET, and replace them all with
request.DATA -- we're going to again be branching away from Django
trunk.
For our uses -- POST and GET are completely different things --
whether you use one at a time or not is unrelated. Things should be
differ
2007/10/18, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
> On Tue, 2007-10-16 at 21:52 +0200, David Larlet wrote:
> > 2007/10/10, David Larlet <[EMAIL PROTECTED]>:
> > >
> > > BTW, no more thought about the way of handling PUT? I've just added a
> > > patch against test.client which add .put() and .d
On 10/17/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> However, neither decision is binding until at least one other core
> maintainer steps in with some agreement [...]
Here's my 2ยข: use ``request.DATA``, and keep ``request.POST`` around
forever. I quite like the way ``request.GET`` and ``
On Tue, 2007-10-16 at 21:52 +0200, David Larlet wrote:
> 2007/10/10, David Larlet <[EMAIL PROTECTED]>:
> >
> > BTW, no more thought about the way of handling PUT? I've just added a
> > patch against test.client which add .put() and .delete(), I'm waiting
> > for (a) reaction(s) to add tests and do
2007/10/10, David Larlet <[EMAIL PROTECTED]>:
>
> BTW, no more thought about the way of handling PUT? I've just added a
> patch against test.client which add .put() and .delete(), I'm waiting
> for (a) reaction(s) to add tests and documentation.
>
Sorry for insisting on that point but this is imp
2007/10/8, Peter Nixon <[EMAIL PROTECTED]>:
>
> Hi David
>
> Thanks for doing this. I have written a patch for mod_python and added it to
> the ticket. I have tested it and deployed it with a patched rest api in
> production ;-)
>
Ok, can you add your patch against django.http.__init__.py too, you
2007/10/7, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
> The Resource class is quite as independent from everything as we would
> have liked. I say "we" here because towards the end of the SoC period,
> Andreas and I spent quite a long time trying to loosen a few of the
> couplings between output cl
On Sat 06 Oct 2007, David Larlet wrote:
> 2007/10/5, Malcolm Tredinnick <[EMAIL PROTECTED]>:
> > On Fri, 2007-10-05 at 16:17 +0300, Peter Nixon wrote:
> > > On Thu 04 Oct 2007, Malcolm Tredinnick wrote:
> > > > On Thu, 2007-10-04 at 18:10 +0300, Peter Nixon wrote:
> > > > > I tried to open the fol
2007/10/7, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
> On Sun, 2007-10-07 at 02:39 +0200, David Larlet wrote:
> > The
> > option (3) seems more natural to me to make the difference between
> > what you post and the POST verb, it's more explicit. What about
> > self.PUT in this scenario?
>
> That'
On Sun, 2007-10-07 at 20:02 +0400, Ivan Sagalaev wrote:
> Malcolm Tredinnick wrote:
> > As soon as
> > you start to move to situations where your publically exposed resources
> > don't map more or less one-to-one onto models, things become a lot
> > trickier and we haven't quite solved that
>
> W
Malcolm Tredinnick wrote:
> As soon as
> you start to move to situations where your publically exposed resources
> don't map more or less one-to-one onto models, things become a lot
> trickier and we haven't quite solved that
Weren't custom descendants of the Resource class designed for this? I
On Sun, 2007-10-07 at 11:16 -0400, Malcolm Tredinnick wrote:
[...]
> There are a lot of cases that Andreas' work doesn't cover, since REST is
> a very broadly applicable theory. That was one of the challenges of the
> project: working out what areas needed help and where we would just be
> adding
On Sun, 2007-10-07 at 02:39 +0200, David Larlet wrote:
> 2007/10/6, Malcolm Tredinnick <[EMAIL PROTECTED]>:
> >
> > I had a quick read of it. Looks like you're on the right track.
>
> Thanks for your reactivity.
>
> >
> > The main problem I see with it is that you're over-populating the data
> >
On 05-Oct-07, at 1:23 PM, Peter Nixon wrote:
>> On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
>>> I tried to open the following ticket but it thinks my IP is a
>>> spammer,
>>> so I am sending to the list:
>>
>> If you create an account in Trac, it won't apply spam filtering to
>> you.
2007/10/6, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
> I had a quick read of it. Looks like you're on the right track.
Thanks for your reactivity.
>
> The main problem I see with it is that you're over-populating the data
> structures a bit. If the request is a PUT, you're still populating
> sel
On Sat, 2007-10-06 at 18:49 +0200, David Larlet wrote:
[..]
> I use django-rest-interface too and I have this bug which need to be
> quickly fixed so I submitted a patch which need review on #5682, let
> me know if I need to do something else. I will add a patch for
> modpython too when this one
2007/10/5, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
> On Fri, 2007-10-05 at 16:17 +0300, Peter Nixon wrote:
> > On Thu 04 Oct 2007, Malcolm Tredinnick wrote:
> > > On Thu, 2007-10-04 at 18:10 +0300, Peter Nixon wrote:
> > > > I tried to open the following ticket but it thinks my IP is a spammer,
On Fri, 2007-10-05 at 16:17 +0300, Peter Nixon wrote:
> On Thu 04 Oct 2007, Malcolm Tredinnick wrote:
> > On Thu, 2007-10-04 at 18:10 +0300, Peter Nixon wrote:
> > > I tried to open the following ticket but it thinks my IP is a spammer,
> > > so I am sending to the list:
> > >
> > > http://django-
On Thu 04 Oct 2007, Malcolm Tredinnick wrote:
> On Thu, 2007-10-04 at 18:10 +0300, Peter Nixon wrote:
> > I tried to open the following ticket but it thinks my IP is a spammer,
> > so I am sending to the list:
> >
> > http://django-rest-interface.googlecode.com/svn/trunk/django_restapi/res
> >ourc
On 10/5/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
> Thanks. I have signed up now, but I still cannot for the life of me find a
> link to that page from anywhere. Shouldn't it be a little more prominent?
Yeah, it should; I'll add a couple of links when I get a moment.
Jacob
--~--~-~--~-
On Fri 05 Oct 2007, Tomas Kopecek wrote:
> Peter Nixon napsal(a):
> > On Thu 04 Oct 2007, James Bennett wrote:
> >> On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
> >>> I tried to open the following ticket but it thinks my IP is a spammer,
> >>> so I am sending to the list:
> >>
> >> If you cr
Peter Nixon napsal(a):
> On Thu 04 Oct 2007, James Bennett wrote:
>> On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
>>> I tried to open the following ticket but it thinks my IP is a spammer,
>>> so I am sending to the list:
>> If you create an account in Trac, it won't apply spam filtering to
On Thu 04 Oct 2007, James Bennett wrote:
> On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
> > I tried to open the following ticket but it thinks my IP is a spammer,
> > so I am sending to the list:
>
> If you create an account in Trac, it won't apply spam filtering to you.
And how does one go
On 10/4/07, Peter Nixon <[EMAIL PROTECTED]> wrote:
> I tried to open the following ticket but it thinks my IP is a spammer, so I
> am sending to the list:
If you create an account in Trac, it won't apply spam filtering to you.
--
"Bureaucrat Conrad, you are technically correct -- the best kind
On Thu, 2007-10-04 at 18:10 +0300, Peter Nixon wrote:
> I tried to open the following ticket but it thinks my IP is a spammer, so I
> am sending to the list:
>
> http://django-rest-interface.googlecode.com/svn/trunk/django_restapi/resource.py
>
> tries to set "request.method = 'POST'" in order
I tried to open the following ticket but it thinks my IP is a spammer, so I
am sending to the list:
http://django-rest-interface.googlecode.com/svn/trunk/django_restapi/resource.py
tries to set "request.method = 'POST'" in order to run PUTs through
request._load_post_and_files() as POSTs as _
31 matches
Mail list logo
