Wednesday, November 30. 2005

Cgiapp 1.7.1 Released

I was able to roll a long-needed (and by some, long awaited) bugfix release of Cgiapp this morning. Cgiapp 1.7.1 corrects the following issues:

  • Cgiapp5::run() was corrected to call query() instead of cgiapp_get_query() (which caused a fatal error)
  • Cgiapp::__call() and Cgiapp5::__call() now report the name of the method called in errors when unable to find matching actions for that method.

As usual, downloads are available on my site as well as via SourceForge.

Update: The link on my site for downloading Cgiapp has been broken; I've now fixed it.

Posted by Matthew Weier O'Phinney in PHP at 22:32 | Comments (2) | Trackbacks (0)

Trackbacks
Trackback specific URI for this entry

No Trackbacks

Comments
Display comments as (Linear | Threaded)

hey does this also fix any crashing errors with using call in the first place in php4? I could never get that to work right, I think I've asked you about that before.

Another interesting thing I would like you to take a look at, is that I've been doing out of the box simple apache bench tests of different frameworks. Im on macosx tiger dual 1.8 gig of ram etc. and out of the box (so to speak) cgi app, when subclasses with a very simple class that all it does its return "test" (using the setup methods, but no external includes other than cgiapp.php itself) runs about 77 requests per second. A standard simple php file that just echos out test on my same machine runs around 300 requests per second.

Well I also checked out cake and trax, and those respective frameworks (trying same thing, very simple return of single string) i could only get them to bust out 5-11 requests per second. Pretty slow.

But can we make cgi app even faster? You know the code the best and I assume you would be able to substitue faster functions like isset instead of array_key_exists in the main class. Because really, the cgiapp based stuff im doing really only slows down once i start including things. Like if i include html quickform, it drops to 35 requests. Not even adodb slows it down that much.

For reference I was using ab -n 200 -c 10. I know my methods are not very scientific, I was just trying to get a handle on estimated speeds.
#1 kenrick buchanan (Link) on 2005-11-22 13:08 (Reply)

Hmm -- I wasn't aware of any crashing errors with using __call() on PHP4. Of
course, that may be because I've primarily used it on PHP5. If you could give me
a sample of code that you know crashes, I'll definitely test it.


I have to say, I'm glad that Cgiapp is outperforming other frameworks, though
I'm disappointed that it slows down so much. I suspect that's largely due to the
overhead of using a class in the first place. However, there are definitely some
things that could be done to speed up the code -- your example of isset() vs.
array_key_exists() is certainly one of them.


I personally feel that Cgiapp is in need of a pretty big audit, and then a
ramping up to include many of the features found in the latest versions of the
perl CGI::Application, and this is my goal for Cgiapp 2.0.0.


If you'd be interested in helping that process, please contact me!
#1.1 Matthew Weier O'Phinney (Link) on 2005-11-23 09:40 (Reply)

Add Comment

Standard emoticons like :-) and ;-) are converted to images.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA