go grab your copy!

I’ve recently received a contribution from Michael Gauthier. I took the liberty to tweak a bit and now memcache.php can flush individual server (no flush all servers yet).

File is now updated and you can get it from here.

PS: I didn’t receive any feedback from pecl guys about my previous update. I’ll post this to them again. I’ll announce when this version is in pecl/memcache CVS.

enjoy.

I’ll be maintaining the code through the time as well. Hope you guys/gals find it useful.

PS: I’m planning to add more functionality to the memcache.php in the coming days. Candidates:

• Delete/Expire a cached value
• Move stuff from server to server

Let me know if you have any other ideas.

Update on memcache.php:

• Small bug fixed on parsing the bucket Ids.
• Distribution license is now PHP license.

Anyways, I decided to rip write my own. Totally based on the original apc.php (I even recycled some functions) and apart from completeness, here is a memcache.php that you can get stats and dump from multiple memcache servers.
Here is a screenshot:


And here is the the source code.

As usual, this piece of software comes with the warnings:
- Don’t expect something complete, might have bugs and security problems etc.
- Do not install on a prod environment unless you’re sure!
- Feel free to add stuff to it, I’ll put it to google code or sf.net soon.
- Feel free to request features. (no I’m not planning a backup tool , there is memcache-tool for that)
- Enjoy!

Update: Small parse error is fixed

PHP may be the most popular Web scripting language in the world. But despite a large collection of nails, not every tool is a hammer. So when should it be used, and when would another dynamic programming language be a better choice? We identify its strengths and weaknesses.

For the ones, who doesn’t know about CIO, their target audience is managerial. not developers.
So potentially reader will be your manager and they’ll get this info as a reference.
I’m copy/pasting some parts of it for your convenience. Let’s assume your manager does not know about PHP (I hope not) and you’re about to convince him/her to use PHP on a project. What whould he/she think after reading this?

When should you use PHP?

• Creating an intranet site.
• Prototyping an application that will be converted to Java or some other language.
• Creating a Web database application.
• Deploying an inexpensive or quick solution.
• Using ready-made apps from Sourceforge.net or other sites.

In general you should not use PHP:

• Where data security is of high importance.
• In Shell or automated scripted applications.
• In enterprise applications where scalability takes higher precedence than economy.

What a short sight!?!? Kenneth Hess the author of the article, is also the new “On The Desktop” columnist for Linux Magazine. Honestly, I would not really expect these claims from Ken Hess.

Please share your comment.

Link: You Used PHP to Write WHAT?!

Read the rest from here: TechNewsWorld

slashdot reports

Wow. I wonder when the prod version will be out. They better release it soon.