Well, some work is already done: - Github Organisation: HTTP Message Strategies Interop <https://github.com/http-message-strategies-interop> - pre-draft PSR HTTP Message Strategies <https://github.com/http-message-strategies-interop/fig-standards/tree/http-message-strategies/proposed/http-message-strategies> - Common interfaces for HTTP Message Strategies <https://github.com/http-message-strategies-interop/http-message-strategies> - Some examples <https://github.com/http-message-strategies-interop?utf8=%E2%9C%93&q=example&type=&language=> are also available, notably: - A fork of David Négrier's symfony-httpinterop-bridge <https://github.com/http-message-strategies-interop/symfony-httpinterop-bridge> Currently, the main difference, which is still up for discussion(!):
- ServerAction:__invoke instead of Handler:handle Some arguments for and against __invoke: - Pros, at the Meta Document <https://github.com/http-message-strategies-interop/fig-standards/blob/5d9084b1b65a75cefcccaca6ef6d1e55de4ac82c/proposed/http-message-strategies/http-message-strategies-meta.md#42-why-__invoke> - Pros+Cons, at Issues <https://github.com/http-message-strategies-interop/fig-standards/issues> - Action vs. Handler at PR#5 <https://github.com/http-message-strategies-interop/fig-standards/pull/5> I know, Rasmus and I disagree on __invoke, but I'm willing to go with the majority. For this reason, I invite Rasmus as an organisation member and everybody else who is interested to participate. Bests, Michael On Wednesday, April 26, 2017 at 7:39:46 AM UTC+2, Rasmus Schultz wrote: > > I've set aside friday to write a draft of the handler PSR. We'll see how > FIG and the community responds and then work from there. > > > On Apr 25, 2017 22:44, "Michael Mayer" <mic...@schnittstabil.de > <javascript:>> wrote: > >> At the very least, we should standardize on a HandlerInterface, so that >>> PSR-15 doesn't ship with an identical, incompatible interface for delegates. >>> >> >> I couldn’t agree more. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "PHP Framework Interoperability Group" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/php-fig/B3jtdJA7-6w/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> php-fig+u...@googlegroups.com <javascript:>. >> To post to this group, send email to php...@googlegroups.com >> <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/php-fig/bdefb246-cc43-4ae2-a703-25b8beb288f8%40googlegroups.com >> >> <https://groups.google.com/d/msgid/php-fig/bdefb246-cc43-4ae2-a703-25b8beb288f8%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/95c1312a-138b-400c-b521-bae86931dc70%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
