はてなブックマーク

For a variety of reasons, I've been working on a utility that is best distributed via PHAR file. As has been noted by others (archive.is link, due to lack of availability of original site), PHAR distribution, while useful, is not without security concerns, and I decided to investigate how to securely create, distribute, and update PHAR utilities as part of this exercise. This is an account of my j

Yesterday, a question tagged #psr7 on Twitter caught my eye: #psr7 Request::getHeader($name) return array of single string instead of strings in #Slim3? cc: @codeguy pic.twitter.com/ifA9hCKAPs @feryardiant (tweet) The image linked provides the following details: When I call $request->getHeader('Accept') for example, I was expected that I'll get something like this: Array( [0] => text/html, [1] =>

I'm pleased to announce that as of 22:00 CDT on 18 May 2015, http://www.php-fig.org/psr/psr-7 PSR-7 (HTTP Message Interfaces) has been accepted! The road to PSR-7 The road to PSR-7 was a long and winding one. It started in summer of 2012 as a draft proposal on HTTP clients by Benjamin Eberlei, during which others proposed that perhaps a smaller standard on the HTTP message interfaces themselves —

PSR-7 is now accepted!!! I'm still hearing some grumbles both of "simplify!" and "not far enough!" so I'm writing this posts to demonstrate usage of the currently published interfaces, and to illustrate both the ease of use and the completeness and robustness they offer. First, though I want to clarify what PSR-7 is attempting. HTTP Messages HTTP messages are relatively simple, which is why the pr

As I've surveyed the successes and failures of ZF1 and ZF2, I've started considering how we can address usability: how do we make the framework more approachable? One concept I've been researching a ton lately is middleware. Middleware exists in a mature form in Ruby (via Rack), Python (via WSGI), and Node (via Connect / ExpressJS); just about every language has some exemplar. Even PHP has some ex

This is a post I've been meaning to write for a long time, and one requested of me personally by Evert Pot during the Dutch PHP Conference in June 2012. It details some observations I have of php-fig, and hopefully will serve as a record of why I'm not directly participating any longer. I was a founding member of the Framework Interoperability Group, now called "php-fig". I was one of around a doz

A number of months ago, Ed Finkler started a discussion in the PHP community about "MicroPHP"; to summarize, the movement is about: Building small, single-purpose libraries. Using small things that work together to solve larger problems. I think there are some really good ideas that have come out of this, and also a number of questionable practices1. One piece in particular I've focussed on is the

One key new architectural feature of Zend Framework 2 is its new module infrastructure. The basic idea behind modules is to allow developers to both create and consume re-usable application functionality — anything from packaging common assets such as CSS and JavaScript to providing MVC application classes. As an example, for my own site, I've created: a "Contact" module for rendering and processi

Welcome! I'm Matthew Weier O'Phinney. I am a software engineer and architect, PHP expert, standards developer, and product manager. I create the tools that PHP developers use to build and deploy their applications, from APIs to content management systems. In addition, I am: He/him. A husband. A father of two wonderful children. A tangle artist. An open source software developer and advocate. Seria