Hello everyone, I have been waiting to announce this until after I finish with PSR16, but there's no time like the present.
I have been working on the routing PSR for some time now, given my passion and experience at integrating 5 different routers into PPI Framework Engine. I have spoke with a few others about this over the past while i.e: MWOP and others. I would be happy to push forward this PSR, by way of Editor, by partnering up with someone (MWOP?), since we both have the experience at building routing interop engines. On the basis that someone is willing to sponsor me. What do we say, is it time to release the cracken ? Many thanks, Paul On 18 Nov 2016 1:01 p.m., "Damiano Petrungaro" <damianopetrung...@gmail.com> wrote: > What do you think about an interface that will be used by RouterInterface > for dispatch an event using a specific method? > In this way the dispatching implementation will be bounded inside a single > RouterInterface (so we could imagine different RouterInterfaces and > everyone will have a RouterDispatcherInterface implemented). > > It's ok to put the dispatching is somewhere else on the implementation > level, but i would like to put it inside to PSR. > > On Fri, Nov 18, 2016 at 7:06 AM Benni Mack <benjamin.m...@gmail.com> > wrote: > >> Hey Hari, >> >> On 18 Nov 2016, at 06:27, Hari K T <kthar...@gmail.com> wrote: >> >> I believe , we should allow Router to do one thing, finding / matching >> the route, generating the route. >> >> Well, I think it should exactly do one thing - namely finding/match the >> route. The generation is IMHO separate, and belongs to a route generator or >> even URI/URL generator. >> >> I agree, dispatching is somewhere else on the implementation level... >> >> Best, >> Benni. >> >> -- TYPO3 Core Team Leader >> Support the project: http://typo3.org/donate/ >> >> -- >> 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/Fj0QoGB1xLU/unsubscribe. >> To unsubscribe from this group and all its topics, 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/A8BB6ABD-75E9-4678-9180-F6EE02FA2A4E%40gmail.com >> <https://groups.google.com/d/msgid/php-fig/A8BB6ABD-75E9-4678-9180-F6EE02FA2A4E%40gmail.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/CAOOfSh5-QJYg%3D77HVqDT5pHo5tuymc3vAsKrQm93S > W%3DqKMMzYQ%40mail.gmail.com > <https://groups.google.com/d/msgid/php-fig/CAOOfSh5-QJYg%3D77HVqDT5pHo5tuymc3vAsKrQm93SW%3DqKMMzYQ%40mail.gmail.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/CAKxcST9KiOSi1auXTNgxxU5mP1-_X4Rr4xEfwQC4UgZcrnpaBA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
