StreamableInterface deserves its own PSR

[Alexander Makarov]

PSR-7 StreamableInterface looks very generic and, in my opinion, could be separate PSR. It’s OK as is in PSR-7 though since multiple interfaces could be implemented so there's no need to reject PSR-7 and wait till another one is completed.

What do you think?

[Larry Garfield]

Both URIs and Streams could stand to be their own PSRs, frankly. In both
cases, we decided not to split it off for the sake of efficiency. That
is, if we did that we'd not take PSR-7 to a vote for at least another
year. :-)

A PSR-7-compatible stream PSR is something I could get behind later;
same for URIs. I think some of the changes made to URIs a few months
ago were specifically to make such a compatible object possible.

--Larry Garfield

[hannesvdreken]

I share Alexander's opinion. Although its simpler for psr7 to use its own simplified version for both Response and Request message objects.

But a Stream Interface psr with clear segregation could be useful for eg http clients, reactphp, ...

[Alexander Makarov]

Glad to hear that you can get behind these.

I'm not in any way insisting on blocking PSR-7. Not even suggesting it.