• phploc: PHP Lines of Code January 28, 2010

    With the growing use of continuous integration and static analysis tools hooked into those processes, there is a particular analysis tool that is very useful but rarely mentioned: phploc, the PHP Lines of Code tool. This has been a feature of PHPUnit for some time but has been released as a separate project in the phpunit pear channel. The nature of PHPUnit means that many of these statistics can be collected while the tests are running, which is why it was added to that tool in the first instance.

    (more...)

    Digg This
    Reddit This
    Stumble Now!
    Buzz This
    Vote on DZone
    Share on Facebook
    Bookmark this on Delicious
    Kick It on DotNetKicks.com
    Shout it
    Share on LinkedIn
    Bookmark this on Technorati
    Post on Twitter
    Google Buzz (aka. Google Reader)
  • Tips for PHP Date and Time Functions January 26, 2010

    Here are some little tricks that might be useful to you if you're working with dates and times in PHP:

    • A "Unix timestamp" or "epoch" refers to the number of seconds since 1970-01-01 00:00:00 UTC. (i.e. a point in time in one specific timezone.) A Unix timestamp is never timezone-specific; if you call time() at the same moment on computers in different time zones, you get exactly the same value back.
    • mktime/gmmktime - Passed a number of arguments (day, month, year, etc.), returns a Unix timestamp. mktime interprets its arguments as representing a local time, whilst gmmktime interprets its arguments as a time in the time zone UTC. (That is, given the same input gmmktime returns the same results everywhere; mktime returns timezone-specific results.) Note that in this case, the gm- prefix affects how the input is interpreted.
    • strftime/gmstrftime - Passed a Unix timestamp and format string, and returns a string. In strftime's case, the string is the time according to the current timezone, whilst gmstrftime returns the time in the UTC timezone. (Given the same input, gmstrftime returns the same time in all timezones (though not necessarily the same string--the actual string may be different if the locale is different) whilst strftime returns timezone-specific results.) Note that in this case, the gm- prefix affects the output string.
    • strptime - Inverse of strftime/gmstrftime: passed a time string and a format string, and returns an array representing the local time. (This not a great return value; it would have been better to return a Unix timestamp.) The time string is interpreted as a local time; there is no gm- equivalent, or even any way to simulate one, since it ignores the value of date_default_timezone_set. Note that you can impose a timezone on the input string if it contains a timezone abbreviation or offset (e.g. Sun 26 Apr 2009 21:50:35 BST) which the format string reads with %z or %Z.
    • date/gmdate - Passed a Unix timestamp and a format string, returns a string. As with strftime/gmstrftime, the gm- prefix affects whether the result is a representation of the time in the current timezone or in the UTC timezone. Note that the format string is completely different to that of strftime/gmstrftime! (One reason to use this set of functions is for the useful date format constants.) There is no inverse of this function.
    • strtotime - Passed a string in "US English date format", and returns a Unix timestamp. Note that there is no way to override the US date format! strtotime ("03/04/2008") is the 4th of March 2008. Note that this function will parse relative times, like tomorrow and next monday; this is about the only reason to use it.
    • How does PHP know what your current timezone is? It tries a few different places, including the TZ environment variable and the date.timezone ini option. (See date_default_timezone_get for more information.)
    Digg This
    Reddit This
    Stumble Now!
    Buzz This
    Vote on DZone
    Share on Facebook
    Bookmark this on Delicious
    Kick It on DotNetKicks.com
    Shout it
    Share on LinkedIn
    Bookmark this on Technorati
    Post on Twitter
    Google Buzz (aka. Google Reader)
  • Caching for performance January 20, 2010

    Speaker: Rob Allen

    More, now than ever, websites need fast response times and be able to cope under load. As web pages contain more and more dynamically generated content, the challenge is on for PHP developers to develop efficient caching solutions. This presentation will focus on using caching techniques that can be used in a PHP project to increase the performance of a web site. We will look at a variety of caching techniques, showing practical implementations and before and after statistics. We will also cover the cache storage options available and when you might use one over another. We will also address how to get browsers to cache content for us using HTTP headers.

    Play
    Digg This
    Reddit This
    Stumble Now!
    Buzz This
    Vote on DZone
    Share on Facebook
    Bookmark this on Delicious
    Kick It on DotNetKicks.com
    Shout it
    Share on LinkedIn
    Bookmark this on Technorati
    Post on Twitter
    Google Buzz (aka. Google Reader)
  • Learning PHP 5.3 by writing your own ORM January 11, 2010

    Creating an ORM for PHP is not an everyday task but writing one is a good way to improve your PHP skills, especially if you use some of the additional features PHP 5.3 adds to the language. There are many excellent ORMs (Object Relational Mappings) already in existence and for a real-world project it would probably better to use one of these, but this tutorial uses the task of creating an ORM as a way to take a look at applications for some PHP 5.3 features.

    (more...)

    Digg This
    Reddit This
    Stumble Now!
    Buzz This
    Vote on DZone
    Share on Facebook
    Bookmark this on Delicious
    Kick It on DotNetKicks.com
    Shout it
    Share on LinkedIn
    Bookmark this on Technorati
    Post on Twitter
    Google Buzz (aka. Google Reader)
  • Advanced CouchDB January 5, 2010

    Speaker: Jan Lehnardt
    Learn how to use CouchDB replication for load-balancing, fault tolerance, offline work and backup. We are showing how to set up each and what you need to look out for.

    Finally, this talk is sprinkled with neat tricks and best practices for deploying CouchDB. Which load balancers are people using, how to make the best use of caching, etc.

    Play
    Digg This
    Reddit This
    Stumble Now!
    Buzz This
    Vote on DZone
    Share on Facebook
    Bookmark this on Delicious
    Kick It on DotNetKicks.com
    Shout it
    Share on LinkedIn
    Bookmark this on Technorati
    Post on Twitter
    Google Buzz (aka. Google Reader)