Skip to content


Rebrand RESTMethod #80

aGHz opened this Issue · 2 comments

2 participants


RESTMethod as it currently exists doesn't really have much to do with REST, it simply handles an HTTP-aware url endpoint. Conforming strictly to HTTP is only one of the tenants of REST, and RESTMethod doesn't go beyond that. I propose renaming it to HTTPResource (or potentially HTTPMethod but that introduces confusion with existing vocabulary - GET, PUT, etc are officially called HTTP methods) to better reflect what it does.

@amcgregor amcgregor was assigned
Marrow Open Source Collective member

I'll re-name and deprecate the old name.


Actually, after realizing that RESTMethod doesn't continue dispatching, I've taken to calling it HTTPEndpoint in my code. Since it can't have sub-resources, HTTPResource would also be a misnomer.

@amcgregor amcgregor closed this in 71ff656
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.