PerlDancer / PerlDancer/Dancer2
Support HTTP extensions beyond HTTP 1.1 spec
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 604
- Forks
- 288
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
(Following on from @shadowcat-mst's comment in #595)
The current Runner, Request and Route classes limit the requests method to only those allowed under the HTTP 1.1 spec. There are extensions to the HTTP spec such as WebDAV, that allow further request types.
The DSL is flexible enough to to allow users to add support keywords for such extensions. Do we want to limit Dancer2 to HTTP 1.1 request methods only ?
Assuming we want this flexibility; what's the best way to implement it?
(As a possibly leading idea; the changes in #595 looks likes it could easily be reworked into standalone Middleware)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review how the Runner, Request, and Route classes currently restrict request methods, then read the related changes and discussion in #595. Determine whether extension methods should be supported and how the DSL and proposed standalone Middleware would provide that flexibility; the issue is complete when an agreed implementation approach and its expected behavior are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100