Re: PSR-7 Alternate Proposal

Hi John, How would you implement a middleware which catches an exception thrown by an inner middleware and returns a response instead of allowing the exception to bubble up? On Wed, Feb 22, 2017 at 11:06 AM Michael Mayer wrote: > John, would you mind pushing your

Re: [REVIEW] PSR-13: Link definition interfaces

approach is the right one! Cheers On Wed, Sep 14, 2016 at 4:21 PM Larry Garfield <la...@garfieldtech.com> wrote: > On 09/13/2016 09:28 AM, Josh Di Fabio wrote: > > On Tue, Sep 13, 2016 at 2:50 PM Larry Garfield <la...@garfieldtech.com> > wrote: > >> The standar

Re: [REVIEW] PSR-13: Link definition interfaces

Quoting the meta doc. > Why is a LinkCollectionInterface needed? > In many contexts, a set of links will be attached to some other object. Those objects may be used in situations where all that is relevant is their links, or some subset of their links. For example, various different value objects

Re: [Discussion][Internals] Remove the Interface suffix from PSR naming conventions

Uncle Bob's opinion: http://stackoverflow.com/a/5817904/4498485 On Wed, Aug 24, 2016 at 2:49 PM Larry Garfield wrote: > On 08/24/2016 07:58 AM, Art Hundiak wrote: > > I find it a bit amusing that exact same discussion is taking place here: > >

Re: [REVIEW] PSR-16 Simple Cache

> Different CacheInterface instances MAY be backed by the same datastore, *but MUST be logically independent.* The second clause seems to be needlessly restrictive and appears to be incompatible with decorators. What is the purpose of this clause? On Wed, Nov 30, 2016 at 4:10 PM Larry Garfield

Re: PSR for HTTP clients

This looks pretty good, but I don't like exceptions for 4xx and 5xx responses, which smells of exceptions for flow control. Within the context of HTTP there is nothing exceptional about 4xx and 5xx responses. Rather, whether a certain response status is considered exceptional depends on the