Next steps for Datagram with ReactPHP v3
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- php
- Domain
- networking
Research direction
Start with this issue, the linked ReactPHP v3 discussion, and the event-loop roadmap issue to understand the upcoming compatibility expectations. Review the reactphp/socket component context and compare the possible paths described here. Done means reaching and recording a decision for Datagram's ReactPHP v3 compatibility, release, or deprecation direction.
Written by the indexing model from the issue text.
Description
We're currently moving forward with working on ReactPHP v3 and releasing the roadmap tickets for all our components (see https://github.com/reactphp/event-loop/issues/271 and others). We still have some components that we haven't finalized plans for, especially with the next major version approaching. It's important to address how we can make sure these components are aligned with the upcoming ReactPHP v3.
To give some background information, the reactphp/datagram project has by far the least amount of installations (currently ~400k) compared to the other ReactPHP components (~10M - 50M) and is not required as a dependency by any of them. This project is mostly used for datagram sockets on client and server side, which could also be integrated as part of the reactphp/socket component in the future.
The Datagram component will most definitely receive some kind of compatibility to support datagram sockets with ReactPHP v3. This could lead to a releasing a reactphp/datagram v3, making just the v1 compatible or we could perhaps deprecate this component and reuse the logic elsewhere as needed?
Happy about input on this, so let's discuss possible options and decide on what makes the most sense 🚀
- Dominant language
- PHP
- Stars
- 99
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
a11y admissions.uiowa.edu needs grooming SiteImprove best practice
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Save States Menu Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
pluginsGLPI/datainjection#673 ·