On 01/08/2016 11:38 AM, Carl Meyer wrote: > On 01/08/2016 04:51 AM, Markus Holtermann wrote: >> Nitpicking, I would also name the settings variable MIDDLEWARES >> (i.e.plural) as it is a list of middlewares, not just one. > > Well, this is a matter of some debate :-) See e.g. > https://github.com/rack/rack/issues/332, where a number of people > fervently argue that "middleware" is a "mass noun" along the lines of > e.g. "furniture", and that it is even incorrect to say "a middleware" > (much like you would never say "a furniture"); instead we should always > say "a middleware component." > > I think those people are fighting a lost battle; the usage of > "middleware" as singular is already well established in the Python > world, even outside Django; people frequently talk about "a WSGI > middleware." > > That said, my ear still prefers "middleware" as both the singular and > the plural (there are such words in English) and dislikes "middlewares." > So I'd prefer to stick with MIDDLEWARE and haven't changed it in the > spec. But if most people think MIDDLEWARES is better, I won't stand in > the way. > > We could also go with something like MIDDLEWARE_FACTORIES or > MIDDLEWARE_PIPELINE and avoid the issue altogether :-)
To take it one level up, historically speaking, using the term "middleware" to mean "something between the web server and a web app's controller/view" is questionable to begin with; note the wikipedia page for "middleware" doesn't even mention this use of the term once. So another option is to find a different term entirely and let the word "middleware" die out from the Django lexicon. One advantage of this would be that we wouldn't have to keep talking about "new-style" vs "old-style" middleware :-) But on the whole I think this is fighting a lost cause too - there are WSGI middleware, Flask has middleware, Rack has middleware. So wikipedia and historical usage aside, our use of the term is by now already well established in the web-frameworks world. I think changing to a different word will probably create more confusion than anything. Carl -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/569009A7.3030003%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
