Subscribe
The PHPUgly podcast - hosted by Eric Van Johnson, John Congdon and Thomas Rideout - has posted their latest episode: Episode #111 - A Failed Transaction.
Topics in this new episode include:
You can listen to this latest show either using the in-page audio player or by downloading the mp3 directly. If you enjoy the show, be sure to subscribe to their feed and follow them on Twitter for updates when new episodes are released.
Matthew Weier O'Phinney has posted the latest in his "deployment with Zend Server" tips today, part five of eight. In this latest post he talks about setting the status of a job.
This is the fifth in a series of eight posts detailing tips on deploying to Zend Server. The previous post in the series detailed how to secure your Job Queue job scripts. Today, I'm sharing some best practices around writing job scripts, particularly around how to indicate execution status.
When he talks about the "status" of a job he's referencing the return code that's provided back to the executing script sharing the pass/fail status of its execution. He shows how to use the ZendJobQueue object and the setCurrentJobStatus to return a constant, either "FAILED" or "OK". He shows how to use it in an isolated example, outputting the results back as a plain text message that can be found in the "Output" tab of the job.
In his latest blog entry, Marco Tabini talks about how we, the community, have "failed the PHP brand" through its overuse (such as in application names of things written in the language).
This is, I believe, a major point of failure for the PHP community. As many have pointed out to me more than once (not that I had anything to do with it, or that I would be able to do anything about it), allowing PHP-related applications to contain the word "PHP" is a major mistake, because it dilutes the value of the brand itself by allowing the quality of PHP to be associated with the value of products that have nothing to do with PHP proper.
He mentions that searches for things like "php vulnerabilities" come up more with things for apps written in PHP and less with results about PHP itself. He even suggests that there isn't a really useful application type that has a PHP-written option that doesn't use the PHP "brand" in its title. He finishes it off with three simple rules that he suggests will help to dilute the PHP brand - don't use it in your application title, always reference that PHP is a trademark of the PHP group (and that there's no association between you), and use the PHP logo in only a descriptive way.
In his latest blog entry, Marco Tabini talks about how we, the community, have "failed the PHP brand" through its overuse (such as in application names of things written in the language).
This is, I believe, a major point of failure for the PHP community. As many have pointed out to me more than once (not that I had anything to do with it, or that I would be able to do anything about it), allowing PHP-related applications to contain the word "PHP" is a major mistake, because it dilutes the value of the brand itself by allowing the quality of PHP to be associated with the value of products that have nothing to do with PHP proper.
He mentions that searches for things like "php vulnerabilities" come up more with things for apps written in PHP and less with results about PHP itself. He even suggests that there isn't a really useful application type that has a PHP-written option that doesn't use the PHP "brand" in its title. He finishes it off with three simple rules that he suggests will help to dilute the PHP brand - don't use it in your application title, always reference that PHP is a trademark of the PHP group (and that there's no association between you), and use the PHP logo in only a descriptive way.
@phpdeveloper.org