OK maybe not to you, but it has just occurred to me, and things don't come to me all that fast these days. Cron jobs. [...] You can have a directory inside your webroot called "cron" (imaginative eh?) with scripts in there that are run via cron.

His method uses the cron daemon on the machine to invoke lynx and call the web page through its url. Of course, there are advantages and disadvantages of the method (including having the script open to the world - scary). Be sure to check out the comments for other suggestions from fellow developers.

For people new to OOP and are comfortable with 'classic' procedural php, you may be wondering why should you even bother to learn object oriented concepts...why go through the trouble?

He has several suggestions included in the post like:

• PHP is moving in an OOP direction [...] So, to really understand and use these frameworks properly, you need to understand object oriented PHP.
• Object oriented PHP really begins to shine as the project becomes more complex, and when you have more than one person doing the programming.
• OOP is the modern way of software development and all the major languages [...] it only makes sense (in terms of career,) to keep your skills up-to-date.
• OOP based PHP is much easier to maintain and update

He also suggests a method for developers to get started with OOP in PHP - how to plan out a project and think in objects rather than procedurally.

Most modern programming languages are based on an OO approach and don't even allow for procedural coding anymore (for instance in languages as Java, C++, C#, Python, and Ruby). Explaining OOP goes beyond the scope of this article, so for understanding OOP in PHP I'd like to point you in this direction. For now let's just say that OOP is about creating relatively small objects with specific functions that interact with each other to form a complete application.

Right off, he lists two advantages to using OOP methods (reusability and better structure) and a disadvantage (can be more time consuming to write). He does still recommend it though to any "serious PHP developer taking on serious projects". He illustrates the point with some of his own experience - an application for a real estate firm.

The choices for this poll were "Performance", "Easy to work with", "Being web-like", "Varied choice of tools", "It has good community back up", "None". Coming out on top was the performance factor with a vote percentage of 20.3%. Next on the list was that it was easy to work with at 15.2%. And, coming in at number three (just barely) - the varied choice of tools that it offers.

They have a new poll up this week too, with a timely question on a topic a lot of PHP developers are working with right now - "Which is the Most Common Design Pattern?" Head on over and cast your vote today!