Re: re-thinking middleware

Hey guys, +1 as well, this is really great work, on both patches! Modifying the middleware stack mid request would be very useful for us. We currently run 3 copies of the same code, with essentially different urls.py and middlewares loaded, each one is used to run a variation of the site, for

Re: CSRF Middleware/SSL/Firefox 3.6.8 bug

n Aug 27, 12:20 pm, Mat Clayton wrote: > >> Any > >> chance of getting some of the core dev's to think about removing > additional > >> SSL checks, as FF 3.6.8 is a pretty major browser to support and this is > >> likely to only get worse as adoption incr

Re: CSRF Middleware/SSL/Firefox 3.6.8 bug

I forgot to mention that as well, not to mention that they can be spooked pretty easily as well, although in this case thats not really a concern. Any chance of getting some of the core dev's to think about removing additional SSL checks, as FF 3.6.8 is a pretty major browser to support and this is

CSRF Middleware/SSL/Firefox 3.6.8 bug

About to file this as a Bug in Trac but after some opinions first. We are running django 1.2, and can't personally reproduce this bug, but some of our users can do. We are using SSL and CSRF to protect our login pages, ( https://www.mixcloud.com/accounts/login/ ) in 99% of cases it works fine. How

Re: Deprecating cmemcache, adding pylibmc

On Tue, Feb 23, 2010 at 2:41 AM, Mike Malone wrote: > > At this point in the release process, I'm not sure we can do > > everything that's being talked about in this thread. Given that we're > > feature-frozen and that there's no way we can spring a completely new > > cache backend on people at t

Re: EmailBackends

On Tue, Feb 23, 2010 at 8:01 AM, Russell Keith-Magee wrote: > On Tue, Feb 23, 2010 at 8:08 AM, Mat Clayton wrote: > > Sorry I probably didn't explain this properly. A composite backend is > half > > the solution, the other part of the problem is deciding which backend to

Re: EmailBackends

s_mail() function. > > Andi > > [1] http://groups.google.de/group/django-developers/msg/a86c5bf950e43d57 > > On Tue, Feb 23, 2010 at 1:08 AM, Mat Clayton wrote: > >> Sorry I probably didn't explain this properly. A composite backend is half >> the solution, the

Re: EmailBackends

, and ideally any backends used by a composite backend should be independent of each other. Mat On Mon, Feb 22, 2010 at 11:49 PM, Jacob Kaplan-Moss wrote: > On Mon, Feb 22, 2010 at 12:48 PM, Mat Clayton wrote: > > Any thoughts on this as a change to the Email Backend system in djang

EmailBackends

Hey, We run our own custom EmailBackend, and for the most part the new Email Backend system has been fantastic, however recently I just found a limitation, which I'd like to raise briefly to see if anyone else has it, or can suggest an obvious solution Ive missed. We currently have a queued email

Re: Deprecating cmemcache, adding pylibmc

a huge +1 on this, having been bitten by cmemcache multiple times. I know this will be controversial, and probably both totally unrelated but thought I'd bring up some other issues we have with caching: 1. As we keep adding more memcache it gets increasingly painful, some form of consistent hashin

Re: DB optimization docs

the interface? Ive not had time to put together docs/tests yet, but don't expect the doc's to take too long. Does anyone have any recommendation on how to approach the tests? Can't say i'm big on tests, and not sure where to start with these. Mat On Sat, Jan 16, 2010 at 2:03

Re: DB optimization docs

:34 PM, Russell Keith-Magee wrote: > On Sat, Jan 16, 2010 at 8:56 PM, Mat Clayton wrote: > > Great, have to confess I don't know the ORM internals at all, so not sure > > how long this could take me, shall see what I can do. Also any > indications > > of where/wh

Re: DB optimization docs

r anyway. With respect to db support I assume all backend's need support in any patch? Mat On Sat, Jan 16, 2010 at 12:27 PM, Russell Keith-Magee < freakboy3...@gmail.com> wrote: > On Sat, Jan 16, 2010 at 7:52 PM, Mat Clayton wrote: > > I know this isn't really related, but

Re: DB optimization docs

I know this isn't really related, but figure I would bring it up here. When working on optimizing our django app, it became very clear that one of the biggest issues as usual is Indexes, particularly multi column indexes, which at present django doesnt appear to support. I know ticket 373 http://c

Re: DB optimization docs

Thanks, much aooreciated On Fri, Jan 8, 2010 at 3:33 PM, Luke Plant wrote: > On Friday 08 January 2010 14:12:56 Mat Clayton wrote: > > As someone going through this pain right now, this would be very > > helpful. > > > > Mat > > I don't know when I'

Re: DB optimization docs

As someone going through this pain right now, this would be very helpful. Mat On Fri, Jan 8, 2010 at 2:04 PM, Luke Plant wrote: > Hi all, > > I was prompted by this post: > > http://it.toolbox.com/blogs/database-soup/stuff-id-love-to-see-from- > django-36278

Changing the Backend for Error Emails

Hey all, Now that Email Backend's have landed, and we finally got round to rolling it out in to production, I discovered small niggle with our deployment. Currently we use an external email provider to deliver email, and the backends has allowed us to do this fantastically. However when an error o

Re: Proposal for 1.2: built-in logging with django.core.log

+1 for this, another random thought which doesn't do your long post justice. But what are everyone's thoughts about log aggregation, taking logs from X app servers and combining them into a single location, something like Facebook's Scribe. I assume this could be built in as a separate log handler,

Re: #10355 Add support for email backends

with these guys, (exacttarget) if anyone has any thoughts on them please let me know off list. Mat On Wed, Sep 2, 2009 at 3:14 PM, Russell Keith-Magee wrote: > > On Wed, Sep 2, 2009 at 6:46 PM, Mat Clayton wrote: > > I'm sure you have this covered but thought I would thr

Re: #10355 Add support for email backends

I'm sure you have this covered but thought I would throw it into the mix. We are currently having lots of problems with blacklisting and spam filters blocking our email servers, one way we are investigating to avoid this is to outsource the email sending to trusted 3rd party services. We don't send

Re: 1.2 Proposal: django debug toolbar in contrib

I thought one of the more recent patches to DDT made it run Jquery in compatability mode, which should resolve these clashes, probably isn't on all branches though. mat On Tue, Aug 11, 2009 at 6:09 PM, Ulrich Petri wrote: > > > Am 11.08.2009 um 16:50 schrieb Alex Gaynor: > > > > This is still t

1.2 Proposal: django debug toolbar in contrib

Hey all, For us of the most useful developments in the django community recently has been the django debug toolbar. http://github.com/robhudson/django-debug-toolbar/tree/master/debug_toolbar This seems to be branching and growing very rapidly on github, however lots of branches are appearing and

Re: Django 1.1

Awesome work guys, congrats. Been running off trunk in production for a while now, looking forward to see what 1.2 brings :) Mat On Wed, Jul 22, 2009 at 8:16 AM, Michael Kerrin wrote: > Hi, > > Thanks for the update, I am looking forward to the release there is a lot > of good stuff in there. >