Arnold Daniels has posted some thoughts on a topics recently featured in a cover story by php|architect - EAV modeling.

I had seen this db structure in other project, but didn't know that it was called EAV. For those who don't read php|architect, EAV describes a method of saving a large set of attributes, only some of which apply to an individual entity. Normally you would create a table, with a row for each entity and save each attribute in a column. With EAV you save each attribute as a row.

He suggests two ways to do the modeling - the more "common" way and an alternative way that splits up the data types to make querying simpler (into scalars and arrays). A sample database structure and example query for it are included.

On the Debuggable blog, Nate Abele has posted a request for opinions on a topic that's been lighting up the PHP mailing lists (and other social media) lately - the alternative array syntax for PHP.

Well, there's a patch available, but 2/3 of the active PHP committers (who participated in the vote) voted against its inclusion. However, of the end-users participating in the discussion, 17 out of 20 voted in favor. Shortly before the voting was concluded, there was a call for some user-land input, so I decided to humbly submit my two pennies.

His comments support the idea, noting that arrays are "our bread and butter" for the language and should be updated to make them even easier to use (and more in line with the declarations of other variable types).

Brian Shire has posted a new tutorial talking about some of the benefits of caching the functionality of your website (with things like APC, not file or database caching):

Opcode caches save energy, expenses, improve overall user experience on web sites, and it's often one of the simplest optimizations to implement. This article will explain the basics of installing, configuring, and tuning an opcode cache for PHP, the Alternative PHP Cache (APC).

The article focuses on how the APC works and how to get it up and working on your installation (as pulled from the pecl repositories). They look at some of the functions the extension's API includes (like ap_cache_info or ap_store for manual caching) as well as some more advanced topics like locking performance, working with TTL, cache priming and filtering.

In this new post to his blog, Ian Selby talks about a method to "pump up" your web site's performance to give the most to your visitors - the APC cache.

Nothing's cooler than writing a bad-ass site or application and watching it gain popularity and a significant user base. By the same token, nothing's more frustrating that watching your app fall on its face when its running under high load. [...] Before you say, "throw more / better hardware at that mo-fo", why not take a moment and learn about APC: Alternative PHP Cache...

He describes the caching software - what it is and how it can help you and your application - and includes examples using a CacheManger class to store and set values quickly and easily.

In this new blog post today, Evert Pot shares some thoughts on a custom solution he was looking to create as an alternative for PHP's serialize function.

I wanted to build this as a helper class for a draft-PHP-RPC server. The reason I needed a custom one was because I wanted to make sure I would be able to spit out PHP4-compatible serialized data, and in the future, when its ported to PHP6, also PHP5-compatible data.

He came across several issues in the development process including the slowness of his method compared to serialize() and a lack of a way to tell if two variables reference the same data. If you'd like to check out what he has so far, he's 0 comments voice your opinion now!
serialize phprcp server data alternative serialize phprcp server data alternative