The term "frame" means nothing to me - I assume the analogy is to stack frames? If so, that is something of a stretch.
I feel the term "frame" is going to require a somewhat confusing explanation. I've suggested the term "delegate", because that's all these objects are - they're just delegates that dispatch the next middleware, so something like MiddlewareDelegateInterface would be more meaningful, in my opinion. Most programmers should already know what a delegate is. Any opinions on this? On Tuesday, July 12, 2016 at 4:26:42 PM UTC+2, Rob Allen wrote: > > Hi, > > In the proposed PSR-15, there's a FrameInterface. > > Where did the word "Frame" come from and in what context is it used. It > means nothing to me and I don't think I'm alone in having no clue how I > would be able to infer that $frame might have a next() method. It's very > weird and I think it's a negative when looking at the function signature as > it's a meaningless word unless you know some back story that I clearly > don't? > > I would love an explanation as it looks to me like an area of confusion > for people new to writing middleware. > > For what it's worth, I don't especially mind the interface itself, though > I'm not sure what it adds other than more typing. It's the choice of name > that I'm questioning. > > Regards, > > Rob... > -- 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/0fef4f27-d4d6-46e6-92cb-17f8fd3561d6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
