We were joined today by Nicolas Grekas in a guest appearance from Symfony. Nicolas had a number of concerns he wanted to bring up to the working group directly. There's three key takeaways from today's call that are relevant:
1) Nicolas brought up the naming question (again). The "task" naming is one of the hangups for a number of people, because every single existing implementation in all of PHP and Javascript for what PSR-14 calls tasks calls it "Events" today. While it's less common outside of PHP, PHP is obviously the primary constituency and Javascript the most likely "second language" for PHP devs. Renaming "task" to "Event" and then removing the parent marker interface is on the table for consideration. (If you have feedback here that hasn't been offered and considered yet, it is welcome.) 2) Removing the parent marker interface would necessitate splitting the Provider into two, one for tasks/events and one for messages. We are going to experiment and see how viable that is and if it would have any unpleasant (or pleasant for that matter) side effects. 3) Nicolas also argued in favor of making the provider take an opaque string rather than the event object itself to determine what listeners are relevant. The main arguments in favor of doing so are a small performance boost in a common case and easier support for dynamic event names (based on user configuration, for instance.) The arguments against are that it's vastly less flexible for anything but that one common case, and the performance difference is not significant. We're going to mull this one over further, but if I can editorialize a bit I think the arguments for changing this are not very compelling. That's it for now. Feedback on the above points is, as always, welcome here on the list. --Larry Garfield -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/2388088.lUnPuxIxTj%40vulcan. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: This is a digitally signed message part.
