Contents tagged with PHP Wincahe
-
Debugging WINCACHE using Visual Studio – Cache management
-
Debugging WINCACHE on Windows using Visual Studio - Basic
In this post I am going to talk about basic tools you will need as well as basic steps which will enable you to start debugging WINCACHE. I will talk about a way to debug WINCACHE running in both PHP CLI as well as CGI version. I am planning to write a series of blog post which will be helpful in debugging WINCACHE. This is just the beginning. So please be patient and forgive me if some of the posts sound for novice user. All my post will assume that you are debugging PHP CGI running under IIS using FastCGI. This means using the non thread safe version of PHP/WINCACHE and IIS running PHP files successfully. I believe the same can be applied to thread safe version of WINCACHE/PHP running under Apache but I do not guarantee that.
-
Final RTW version of WINCACHE 1.0 released
I am extremely proud to announce that we have released the final RTW version of WINCACHE 1.0. Please look at the forum announcement of the same at http://forums.iis.net/p/1162808/1925444.aspx#1925444 which contains all the details about the release. I would strongly recommend everyone running Beta/RC version of WINCACHE 1.0 to upgrade to the final RTW release. If you installed WINCACHE 1.0 RC from Microsoft Web Platform Installer, you can use the same to upgrade to RTW. Upgrade from RC to RTW is supported through WPI. If you have installed WINCACHE 1.0 RC/Beta manually, you will need to install the new binaries manually. Here are the steps:
-
Enabling WINCACHE on per site basis
With WINCACHE 1.0 RC one can configure parts of WINCACHE solution on a per site basis. As you know WINCACHE has two kinds of cache namely output code cache and file cache. With RC release, you have the ability to turn output code cache on a per site basis. We have got a new WINCACHE directive named WINCACHE.OCENABLEDFILTER which can be used to enable/disable output code cache on a per site basis. This INI directive can take a string which is list of comma separated numbers. Each number in the string represents a valid site id which is a unique identity IIS gives to each Web Site when the site gets created. All the site id included as part of this string will actually toggle the value of WINCACHE.ocenabled while running WINCACHE functionality. Example, if you have below in your PHP INI file:
-
WINCACHE statistics page - login dialog keeps popping up
As you know we released WINCACHE 1.0 RC early last week. We have got some good response for all the new features and bug fixes the RC release contains. If you haven't tried the RC version you should definitely try it out. We also included a brand new WINCACHE statistics page which displays lot of useful statistics about the cache. However there were people in the forum who complained about getting the login dialog again and again no matter what they pass as login/password.
-
WINCACHE 1.0 RC - Breaking Change
This breaking change has got an interesting story. While we were developing this WINCACHE module and I got the initial build to test I realized that the only way to test it using CGI version of PHP. Well I being a developer myself checked out the sources and commented out the code to make it run for CLI version of PHP too. Life was good for me and I found some bugs. Eventually I did move to CGI but I wanted the support for CLI too. I asked my developer to enable it for CLI too. The developer obliged to this and I was so happy getting this on regular builds.