Skip to content
This repository

Rebrand RESTMethod #80

Closed
aGHz opened this Issue December 09, 2011 · 2 comments

2 participants

Adrian Ghizaru Alice Zoë Bevan–McGregor
Adrian Ghizaru
Collaborator

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.

Alice Zoë Bevan–McGregor
Owner

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

Adrian Ghizaru
Collaborator

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.

Alice Zoë Bevan–McGregor amcgregor closed this in 71ff656 December 12, 2011
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.