A new version of PHPCache is available.

This one has 5 new methods:

PHPCache::set_expire($key)
Which will set the expiration of the cache record for $key in the past, I think this method has some advantages over deleting the key all together.

PHPCache::remove($key)
Will completely remove the row.

PHPCache::clean_up()
This method will be called when ever you construct/configure a new PHPCache object with PHPCache::configure($database) method and does two things:

1 - Will delete all the old keys on the table, you can control how often this happens with 2 constants:
PHPCACHE_GC_PROBABILITY & PHPCACHE_GC_DIVISOR
If you set PHPCACHE_GC_PROBABILITY to 10 and PHPCACHE_GC_DIVISOR to 100, then when ever you configure the PHPCache object with PHPCache::configure($database); there will be 10% chance that the garbage collector will delete the old rows.
The default value is 1%.

2 - It will optimize the table PHPCache is using, you can also control how often this happens through 2 other constants:
PHPCACHE_TO_PROBABILITY & PHPCACHE_TO_DIVISOR
It works similar to #1 and default value is 10%.

PHPCache::gc()
Will delete the old rows anytime you call this method, it doesn’t care about PHPCACHE_GC_PROBABILITY & PHPCACHE_GC_DIVISOR
One place to use this would be a cron tab.

PHPCache::optimize_table()
Will optimize PHPCache’s table and doesn’t care about
PHPCACHE_TO_PROBABILITY & PHPCACHE_TO_DIVISOR

This new version has some more minor improvements over the old one too.

Finally today we launched Bloggapedia’s new features and we are very happy with it.
We are not done yet and more features are on their way.

Here is my profile:
http://www.bloggapedia.com/user.php?u=14679

I wrote a post earlier about how jEditable (a jQuery) plugin needed password support and the author of the plugin wrote back and said here is how to add this feature:

$.editable.addInputType(’password’, { … });

You can read more here:
http://www.appelsiini.net/2007/8/custom-input-types
http://www.appelsiini.net/2008/4/autogrow-textarea-for-jeditable

This plugin is really great and we are doing some exciting things on Bloggapedia with it.
We will launch early this week hopefully because we are working on a recommendation engine.

Happy Coding

Those of you who know me know that one of the client projects I’m working on for many years is Bloggapedia.

It started as a categorized collection of blogs and then became a blogging community.

From the very beginning, I always bugged everyone involved to let me make a search engine out of it and a few months back they finally agreed and told me to go for it. So it took me a while to develop the search part and the blogs are manually approved so there is really no junk.

Right now Bloggapedia is a full text search engine (and it doesn’t use MySQL’s fulltext search either, it was too slow ) and it searches all the blogs in the database at the speed of light and the quality of the result is great!

Now, there is another famous blog search engine called Icerocket. Icerocket has so much reputation and it’s name is everywhere BUT I don’t understand why?

For example take a look at the search result for the term “Sushi” on Icerocket:

http://www.icerocket.com/search?tab=blog&fr=h&q=sushi

Now, compare this with Bloggapedia:

http://www.bloggapedia.com/blog_search.php?q=Sushi&=posts

Do you see the difference?

And hey if you are from Icerocket, I can fix this for you