Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / zostay/rakuwapi issues and pull requests
#43 - A working example with an Apache server could be a big win
Issue -
State: open - Opened by tbrowder almost 5 years ago
#43 - A working example with an Apache server could be a big win
Issue -
State: open - Opened by tbrowder almost 5 years ago
#42 - Troubles with installing on latest rakudo and zef
Issue -
State: closed - Opened by Altai-man about 5 years ago
#42 - Troubles with installing on latest rakudo and zef
Issue -
State: closed - Opened by Altai-man about 5 years ago
#41 - http2 question - stream-identifier in p6w response
Issue -
State: open - Opened by ufobat over 7 years ago
#41 - http2 question - stream-identifier in p6w response
Issue -
State: open - Opened by ufobat over 7 years ago
#40 - Use SPDX identifier in license field of META.info
Pull Request -
State: closed - Opened by samcv almost 8 years ago
#39 - Use modern META filename
Pull Request -
State: closed - Opened by zoffixznet almost 8 years ago
- 1 comment
#38 - Add mandatory "perl" META field
Pull Request -
State: closed - Opened by zoffixznet over 8 years ago
#38 - Add mandatory "perl" META field
Pull Request -
State: closed - Opened by zoffixznet over 8 years ago
#37 - Harikiri terminology
Issue -
State: closed - Opened by HotelCalifornia almost 9 years ago
- 1 comment
#37 - Harikiri terminology
Issue -
State: closed - Opened by HotelCalifornia almost 9 years ago
- 1 comment
#36 - Clarify 2.0.4
Issue -
State: closed - Opened by lestrrat over 9 years ago
- 2 comments
#35 - Study the consequences of concurrency and parallelism here
Issue -
State: open - Opened by zostay over 9 years ago
- 7 comments
#35 - Study the consequences of concurrency and parallelism here
Issue -
State: open - Opened by zostay over 9 years ago
- 7 comments
#34 - Returning to the registration routine idea
Issue -
State: open - Opened by zostay over 9 years ago
- 7 comments
#33 - Fix typos
Pull Request -
State: closed - Opened by 0x1F602 over 9 years ago
- 1 comment
#33 - Fix typos
Pull Request -
State: closed - Opened by 0x1F602 over 9 years ago
- 1 comment
#32 - Typos
Issue -
State: closed - Opened by 0x1F602 over 9 years ago
#31 - Beta0x64 patch 1
Pull Request -
State: closed - Opened by 0x1F602 over 9 years ago
- 2 comments
#31 - Beta0x64 patch 1
Pull Request -
State: closed - Opened by 0x1F602 over 9 years ago
- 2 comments
#30 - Update META.info version number
Pull Request -
State: closed - Opened by 0x1F602 over 9 years ago
- 1 comment
#30 - Update META.info version number
Pull Request -
State: closed - Opened by 0x1F602 over 9 years ago
- 1 comment
#29 - Thinking about how to handle protocols directly
Issue -
State: open - Opened by zostay over 9 years ago
- 3 comments
#29 - Thinking about how to handle protocols directly
Issue -
State: open - Opened by zostay over 9 years ago
- 3 comments
#28 - Rename all the p6sgi bits to p6w
Issue -
State: closed - Opened by zostay over 9 years ago
- 10 comments
#28 - Rename all the p6sgi bits to p6w
Issue -
State: closed - Opened by zostay over 9 years ago
- 10 comments
#27 - Define the role of p6sgix.h2c.push-promise in more detail
Issue -
State: open - Opened by zostay over 9 years ago
#27 - Define the role of p6sgix.h2c.push-promise in more detail
Issue -
State: open - Opened by zostay over 9 years ago
#26 - Consider using a Junction for p6sgix.protocol.upgrade
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#26 - Consider using a Junction for p6sgix.protocol.upgrade
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#25 - Kill the 2.x.3 The Error Stream sections
Issue -
State: closed - Opened by zostay over 9 years ago
- 3 comments
#25 - Kill the 2.x.3 The Error Stream sections
Issue -
State: closed - Opened by zostay over 9 years ago
- 3 comments
#24 - Alternate response format for WebSocket?
Issue -
State: open - Opened by zostay over 9 years ago
- 1 comment
#23 - Output supply should be closed by server, not app
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#23 - Output supply should be closed by server, not app
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#22 - Add a diagram for the app lifecycle
Issue -
State: open - Opened by zostay over 9 years ago
#21 - Consider using an application registration routine
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#21 - Consider using an application registration routine
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#20 - Handling HTTP/2 server push with P6SGI
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#20 - Handling HTTP/2 server push with P6SGI
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#19 - How can a P6SGI application push?
Issue -
State: closed - Opened by zostay over 9 years ago
- 4 comments
#19 - How can a P6SGI application push?
Issue -
State: closed - Opened by zostay over 9 years ago
- 4 comments
#18 - Consider how to add buffered input back
Issue -
State: open - Opened by zostay over 9 years ago
#18 - Consider how to add buffered input back
Issue -
State: open - Opened by zostay over 9 years ago
#17 - Modernize HTTP_* headers
Issue -
State: open - Opened by zostay over 9 years ago
- 1 comment
#17 - Modernize HTTP_* headers
Issue -
State: open - Opened by zostay over 9 years ago
- 1 comment
#16 - HTTP/1.1 Trailing Headers
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#16 - HTTP/1.1 Trailing Headers
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#15 - What is the impact of HTTP/2 framing and streams?
Issue -
State: closed - Opened by zostay over 9 years ago
- 4 comments
#15 - What is the impact of HTTP/2 framing and streams?
Issue -
State: closed - Opened by zostay over 9 years ago
- 4 comments
#14 - Use a Supply for p6sgi.input
Issue -
State: closed - Opened by zostay over 9 years ago
- 2 comments
#13 - Consider moving the Promise from application to server
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#12 - WebSocket support
Issue -
State: closed - Opened by zostay over 9 years ago
- 7 comments
#11 - Fix JSON error
Pull Request -
State: closed - Opened by zoffixznet over 9 years ago
- 1 comment
#10 - Look into an extension for handling response backpressure
Issue -
State: closed - Opened by zostay over 9 years ago
- 2 comments
#9 - Consider renumbering section 2
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#8 - Move extensions into a new section and add more extensions
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#7 - Add roast-style tests for P6SGI implementations
Issue -
State: open - Opened by zostay over 9 years ago
#6 - Fix links generated in README.md on github
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#5 - Are the input stream requirements sensible?
Issue -
State: closed - Opened by zostay over 9 years ago
- 2 comments
#4 - Is the error stream sensible?
Issue -
State: closed - Opened by zostay over 9 years ago
- 1 comment
#3 - Encoding Str/Cool/etc. is a pain for middleware
Issue -
State: open - Opened by zostay over 9 years ago
- 6 comments
#2 - Handling Promise status if Supply fails after Promise is kept
Issue -
State: closed - Opened by muraiki over 9 years ago
- 3 comments
#1 - Typo formatting
Pull Request -
State: closed - Opened by moritz over 9 years ago
- 1 comment