ZF-6071: Zend_Http_Client needs a __destruct

Issue Type:
Improvement
Created:
2009-03-19T16:21:31.000+0000
Last Updated:
2009-10-16T06:37:25.000+0000
Status:
Resolved
Fix version(s):
    Reporter:
    Till Klampaeckel (till)
    Assignee:
    Dolf Schimmel (Freeaqingme) (freak)
    Tags:
    • Zend_Http_Client
    Related issues:
    Attachments:

    Description

    At the bare minimum it should call the Adapter's {{__destruct()}}, e.g. {{Zend_Http_Client_Adapter_Socket::__destruct()}}.

    Comments

    Posted by Dolf Schimmel (Freeaqingme) (freak) on 2009-03-19T16:24:40.000+0000

    I'm kinda missing the point here. Why exactly would it need one?

    Posted by Shahar Evron (shahar) on 2009-07-23T16:20:43.000+0000

    Are you saying this because of a problem you encountered or because you think it's correct...?

    Calling the Adapter's __destruct() would be plain wrong IMHO because nobody said one wants a pre-configured $adapter object to be destroyed with the client. For example, I might want to set some stream context options on the socket adapter, capture the peer's SSL cert and then extract it using $adapter->getStreamContext() - maybe even after the client has been destroyed.

    Let me know if there's a good reason for this, or if I can simply close this bug.

    Posted by Shahar Evron (shahar) on 2009-07-23T16:23:08.000+0000

    Resolved by mistake

    Posted by Dolf Schimmel (Freeaqingme) (freak) on 2009-10-16T06:37:25.000+0000

    Closing this issue because no response was given for several months.