Hi! > I think you over estimate the complexity to move something to a clean, > maintained, user friendly API from a over complex, buggy and > unmaintained extension and library (which can kill requests under > certain circumstances too).
No I do not. It doesn't matter if it's maintained or not if the code *works*. However friendly and shiny new components are, it is new development in the application infrastructure, and believe me, I know how much that costs in dev time, qa time, support time, etc., etc. If you ever did such thing, you must know it too. > Again, 2015! That's not now, not tomorrow but 2015! 5.5 is planned to be released next year, isn't it? Users of imap will not be able to use it. I see no reason to set up both them and 5.5 for this fail. > if totally dead and not secure c-client is not a good reason, then I > have no idea what a good reason is :), and again, we are saying: "Heh, Good reason would be extension broken and nobody willing to fix it, or presence of the superior alternative with easy migration path. imap works for its users just fine, and alternatives require installing frameworks with substantially different APIs. So what? We have bugs in many extensions. It is sad that maintainers do not fix them, but so is the nature of the volonteer project. If the extension still works, I see no reason to remove it. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
