#49901 [Bgs]: changing IMAP_CLOSETIMEOUT through imap_timeout() is not implemented
ID: 49901
User updated by: olivier at oxeva dot fr
Reported By: olivier at oxeva dot fr
Status: Bogus
Bug Type: IMAP related
Operating System: linux
PHP Version: 5.3SVN-2009-10-16 (snap)
New Comment:
Hi,
My reproduce code was bogus. You should read IMAP_CLOSETIMEOUT
everywhere. That's why I think you did not understand what I was
saying:
Changing the close timeout seems to have no effect at all :
var_dump(imap_timeout(IMAP_CLOSETIMEOUT , 10)); //returns TRUE, so
change has been commited
//Now, the getter should return 10, right ?
var_dump(imap_timeout(IMAP_CLOSETIMEOUT)); //returns previous default
value, as if nothing were changed
Previous Comments:
------------------------------------------------------------------------
[2009-10-19 10:41:00] jani@php.net
If you don't pass the timeout parameter, imap_timeout() will only
return what it is set to currently. No bug here.
------------------------------------------------------------------------
[2009-10-16 14:50:18] olivier at oxeva dot fr
Description:
------------
It seems changing IMAP_CLOSETIMEOUT through imap_timeout() function is
not implemented. Also, the returned value seems arbitrary (when using
imap_timeout with one argument).
If this usage is not implemented, documentation should be updated.
Reproduce code:
---------------
<?php
var_dump(imap_timeout(IMAP_CLOSETIMEOUT));
var_dump(imap_timeout(IMAP_WRITETIMEOUT, 10));
var_dump(imap_timeout(IMAP_CLOSETIMEOUT));
Expected result:
----------------
int(%d)
bool(true)
int(10)
Actual result:
--------------
int(%d)
bool(true) //as you can see, function tells that update was
successfull
int(0) // ... but value has not been updated
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=49901&edit=1
Thread (3 messages)