json

Lorna Mitchell is back with another post in her "Building a RESTful PHP Server" series today with this new post showing how to work with output handlers (her focus is on JSON).

Before we start with today's topic, let's refactor our current framework just a little to make templates even more readable:

On the Nelm.io blog today there's a new post (part one of a series) about using Composer and Packagist to manage PHP applications as packages.

I recently set up a new Twitter account that shares links to some of the smaller stories I come across in my news reading for PHPDeveloper.org called @phpquickfix.

I recently had started playing with Gimme Bar more and wondered how easy it’d be to set it up as a backend repository for some links.

Wazi:Applications built with the Google Web Toolkit (GWT) can work with both XML and JSON data.

If you've been following my blog, you might have noticed that lately I've started doing quite a lot of Node.js development alongside PHP.

Based on conversations I've had in various conferences, I'm by far not alone in this situation - using Node.js for real-time functionality, and PHP (or Django, or Rails) for the more traditional CRUD stuff.

Johannes Schluter has shared a handy mysqlnd plugin that he's written up that does two common things at once when you're pulling data from your database and pushing it into JSON - a mysqlnd_query_to_json function.

In a a new tutorial posted on his blog Martin Sik shows you how to "steal" the "did you mean..." functionality that Google's sites currently offer.

His example uses cURL to get the current Google request URLs and fetch the associated results.

I've introduced Gearman into a project I'm working on, and since a few people have asked I thought I'd share my experiences.

Basically, this application generates some PDFs from a variety of data sources, makes images, and emails it. Since the whole data processing, image handling, PDF generation process is fairly heavy, I'm putting the requests to generate these onto a gearman queue and having some workers process the jobs.

The eventual aim is to bring up EC2 instances (or php-specific cloud hosting perhaps?

Many of you might already know this, but I wanted to point out why I think using the Prototype Javascript library is a bad idea.

The biggest problem is actually highlighted in it's name: it changes many of the prototypes of core javascript types.

You might have realized this before, when you tried to 'for(i in arr)' and came across many of the extra functions prototype added.

(and you should have realized at this point this wasn't the proper way to loop through an array anyway.).