Posted by Stas on August 28, 2011
Zend Framework has pretty good OAuth consumer implementation. However, it has no support for implementing OAuth provider, and it turns out that there aren’t many other libraries for it. Most examples out there base on PECL oauth extension, which works just fine, with one caveat – you have to have this PECL extension installed, while ZF implementation does not require that.
So I went ahead and wrote some code that allows to easily add OAuth provider to your ZF-based or ZF-using application. That should make writing OAuth provider easier.
Note that the code does not implement the whole server – just the OAuth protocol wrapper, you’d still have to do all the work of managing tokens/keys/nonces by yourself. See example server in the repository and the wiki on github for more details on how to do it, but the protocol follows what PECL oauth does pretty closely, so many tutorials for it would be mostly applicable to this one too.
Check out Zend_Oauth_Provider on github, if you want to improve it – please fork and submit pull requests.
Posted in Functions, PHP | Tagged: zend framework, oauth, oauth server | 13 Comments »
Posted by Stas on August 3, 2011
Being at OSCON, I’ve attended one good talk about Python oddities, which got me thinking about language syntax in general.
PHP is notorious among scripting languages for it’s verbose syntax – you have to spell out many things that are much shorter in other languages. Some people think it’s very bad that they can’t be “expressive”, meaning writing more clever code with less keystrokes. Sometimes they are right, sometimes they are not. Let’s consider two examples:
From PHP: 5.4 has a new array syntax:
['foo', 'bar'] which is the same as
I think it’s a good shortcut – because
 is a common expression for arrays (or structures that work like PHP arrays) in many languages, and it is obvious for most people how it works.
What’s an example a shortcut that isn’t good? Python (version 2) has this syntax for exception handling (this was one of the examples in the talk):
except Foo, Bar:
Now what this means: are we catching two exception types, Foo and Bar, or are we catching exception Foo and assigning it to Bar? The correct answer is the latter – it’s exception Foo assigned to Bar. I think it’s bad shortcut – because it uses a comma – which is common expression for lists and enumeration – to separate the type and the parameter. This leads to people writing things like “
except KeyError, IndexError” which doesn’t do what one would expect to.
Pyhton people seem to agree with me, as in Python 3 the syntax has been changed to:
except Foo as Bar:
One could argue it’s not as “expressive” and more verbose – bu it’s definitely much more readable and would lead to less broken code. It’d be even better if they used the word “exception” or try/catch as all the rest of the world does
Some people in PHP community think all “shortcuts” are best to be avoided. I think some of them could be useful, provided clarity is not sacrificed and there’s not “too much magic”. I know it’s subjective but my personal criteria is that if it’s not immediately clear what’s going on for a person with reasonable knowledge of the matter – it’s probably too much magic.
Posted in Engine, PHP | 4 Comments »