Consider an option for an explicit list of allowed methods

[muodov]

Currently, routing code would allow all methods the responders are implemented for. But this behavior makes it inconvenient if one wants to inherit the resource class. The only way to disallow method in a child class is to override all the responders which results in a bunch of useless code.

It would be nice to be able to set some resource attribute to a list of allowed methods.

[kgriffs]

@muodov thanks for the feedback. I'd like to learn more about how you are using inheritance. Could you provide more details on your use case?

[muodov]

@kgriffs Sure. In our application we store objects in mongodb, so in the code we have a base class called DocumentResource which handles all communication with the database. The base class accepts a collection name as an argument and it can get, put, and post objects.
Now, for specific documents we subclass DocumentResource and place the document-specific logic in there. The problem is, we want to provide different sets of actions for different kinds of objects. For example, we need to allow only GET method. In this case we need to explicitly override the parent methods for other HTTP methods so that they set falcon.HTTP_METHOD_NOT_ALLOWED status. This results in a lot of copypasted code and generally is quite error prone.

[pior]

What about:

class MyResource(DocumentResource):
    model = Foo
    on_put = NotImplemented  # https://docs.python.org/2/library/constants.html#NotImplemented

I may also need this. For a similar resource subclass pattern.

[kgriffs]

Another option. This would override the default behavior of allowing all HTTP methods that have a corresponding on_* responder defined.

class SomeResource(DocumentResource):
    allow = ['GET']

[muodov]

@kgriffs I like your suggestion. It feels more natural for people coming from other frameworks, since they have similar concepts.