Can we configure the socket_read_timeout in this version or not??

bye.

As Andrey has pointed out already, client side caching is not available yet. We have some ideas on it but currently no time and resources to implement it in a proper way. If PHP 5_3 comes out in Q1 2008, I doubt we’ll have it ready for a release. As client side caching is a killer feature you can be sure that we won’t forget about it. However the next milestone is a proper version for the PHP 5_3 release. Once that has happened we can pick up the idea again and check if we have resources to implement it.

We are not sure about the Stream API, its a raw bin idea nothing more. No code, no concrete plans. Personally, I’d like to see an experimental branch featuring it and play with it for some days. But do we really need support for streams now that MySQL Proxy is there? Adding MySQL Proxy to your setup is a matter of minutes and Jan is making great progress on performance. Proxy comes with all what you need for load balancing, query rewriting, auto explain and stuff.

Also, do you really want to parse the binary data send over the wire to MySQL using PHP. To be honest, nobody who has ever implemented the MySQL Client Server protocol has fallen in love with it. Its an efficient protocol but Joe Doe PHP user will hate it.

There are few things that might be easier to do within your PHP application using a stream API than using the external MySQL Proxy. For example, I could imagine that if you application uses some sort of DB abstraction layer its much easier to turn on an “auto_explain” for only selected parts of your app but it would be with Proxy.

However, does that really justify adding a stream API? And what do you think will happen to mysqlnd if a power user changes states using the stream API… Again, I’d love to play with it for a minute but I’m afraid that there’s no enough benefit in a stream API to justify the efforts.

Try out MySQL Proxy. Its simple, its fast (enough), its how.