Fixed ZF2-100: Use new naming convention for zend config options#588
Fixed ZF2-100: Use new naming convention for zend config options#588proofek wants to merge 1 commit into
Conversation
|
I disagree. Where come from this new naming convention? |
|
See http://framework.zend.com/issues/browse/ZF2-100 for reference. |
|
When we say don't use underscore, we means $_foo not 'foobar' instead of 'foo_bar'. If we talk about ZendMonitor, you write this 'zend_monitor' and not 'zendmonitor'. |
|
FYI. Socket Adapter's fix is If you run test tests/Zend/Http/Client/Adapter/*, "headers key" bug will block tests . (I would pull-request for ZF2-99 fix later ) |
|
Closing -- intiilapa's comments hit the nail on the head. We're removing underscore prefixes for non-public variables and method names, but encouraging underscore separators for config options. |
|
Well in that case library/Zend/Http/Client.php is broken, as it removes all underscores in config. |
|
First, after the Options proposal is ratified, this will be a non-issue. But secondly, more importantly, normalization allows for both 'keep_alive' and 'keepalive' to both be passed as a config option and all the subsequent classes the ability to read the value for that config value. Also, I don't think this has anything to do with the @ZF2-99 that was reported, that seems like a case of keepalive being passed in, but also not waiting for the socket to finish what it is doing. |
|
Well, if you gonna go for the support of both conventions then Proxy class needs to be changed to accomodate that. At the moment it's broken and will not proxy requests properly. Do you reckon it should check for both proxy_host and proxyhost options then? |
|
I think an Adapter abstract should do the normalization in all cases. However, this is broken, so I think temporarily accepting the pull request above would be fine. I came here after an hour debugging Mink+Goutte, which uses the entire ZF2 in order to function for some unclear reason. |
No description provided.