Control Flow in PINQ
posted on Jul 16, 2008 at 5:48pm with three comments and tagged with PHP, PINQI was a bit bored so I whipped up this little diagram in OmniGraffle of the control flow within the PINQ framework and an application. Most things will seem familiar to programmers who regularly use MVC frameworks. It's actually slightly more complex than what is going on in there; however, I was limited to using 20 object with the demo version of OmniGraffle and so I was rather limited on what I could show.
The one interesting bit in here is the yield resource exception. As I've written in previous posts, it changes control from one controller to another.
Comments
-
Thanks for that. It is among many other things (the way packages are structured, needless complexity in the db package, etc) I need to think over.
posted by Peter Goodman on Aug 6, 2008 at 10:34pm -
This isn't really related to your blog post, but I was perusing your source files on google code and noticed that there is a minor error on your http response list in:
posted by Mike G. on Aug 6, 2008 at 8:36pm
system/functions/http.php -> Http::setStatus()
501 => "Method Not Allowed", is in fact http code 405, not 501.
While it's nice to have an exhaustive list of http response codes for reference, the large majority of these codes have no business being sent out by php... Specifically the 1xx codes, many of the 4xx codes, and most of the 5xx codes. Http 402, for instance is not even used in the current specification. You're never going to need to send out a 408, 413, 414, 504, 505, et cetera because those are all handled by apache for you... just my 2¢.
The full spec can be found here:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html -
Uh .. the link is dead. Nice idea though.
posted by troels on Dec 28, 2008 at 9:34am
Comment