Add a TransactionMiddleware

[Tim Graham]

With new-style middleware, it should be feasible to write a TransactionMiddleware that works properly (as opposed to the version in Django 1.7 and older).

[luojiebin]

Do this middleware want to do the same thing as the one in Django 1.7 except that it applies only to view functions, not including those middleware modules coming after it? Can you explain it in more detail? Thanks.

[luojiebin]

Do this middleware want to do the same thing as the one in Django 1.7 except that it applies only to view functions, not including those middleware modules coming after it? Can you explain it in more detail? Thanks.

to Tim Graham:

With new-style middleware, it should be feasible to write a TransactionMiddleware that works properly (as opposed to the version in Django 1.7 and older).

[Tim Graham]

Florian (apollo13) mentioned this idea in #django-dev IRC but later indicated there may be some problems with it.

[Florian Apolloner]

@luojiebin That is to be decided, the main issue here - as you noted - is supporting ​non_atomic_requests. Any ideas welcome :D

[luojiebin]

But why the previous TransactionMiddleware was deprecated? Only because ATOMIC_REQUESTS can do the same thing as it? But it can not noly apply to views, but also other middleware, which ATOMIC_REQUESTS can't do. So, does the previous TransactionMiddleware cause any problem so that we have to deprecate it? With the new-style middleware, we can handle the previous problem, or we can add new feature to TransactionMiddlware with it?

to Florian Apolloner:

@luojiebin That is to be decided, the main issue here - as you noted - is supporting ​non_atomic_requests. Any ideas welcome :D