Macaw - A Simple PHP Router

Probably shouldn't be "hard" coding the scheme (http). Check $_SERVER['https']. You can make sure this fastcgi param exists with a simple directive in nginx (fastcgi_params):

    fastcgi_param  HTTPS  $https if_not_empty;

Also, the 404 route, should be able to be defined as a custom function:

    Macaw::fourofour(function() {
        header($_SERVER["SERVER_PROTOCOL"] . " 404 Not Found");
        header("Status: 404 Not Found");
    });

Nice. Php's community have -- with the advent of sane dependency management through Composer, no more PEAR yay! -- move to this small composable library style. I think it's a great thing, using Macaw (or Slim, in my case) plus your business logic modelled as raw, SOLID, tested classes gives you an amazing API to work with,both on the PHP side, and on the network side. I haven't needed to use Symfony for anything new lately,though if I was building a huge app from scratch with a larger team, Symfony is where it's at.

Oh, that sort of router...

For a second I thought someone had coded an IP router in PHP. Which would be a really interesting thing to see, if not particularly practical.

I like the "slim" approach on LOC, kudos to that. I would point some - IMO - design problems:

# Static attributes and methods. Are they really needed? They are difficult to test and predict, specially the public attributes.

# The "echo"s on routes. Since every route is a method (encapsulated by one), this behavior could be easily avoided (easier to test and control). You are already using callables, you can easily test (and run) matching routes to execute any callable until a stream is given (on Respect/Rest we learned what a powerful feature it is).

# Lack of tests. Although low LOC, there is much happening, specially on the "dispatch" method (it would be awesome to know through tests what the If's/Else's actually do and prevent).

# Why (as mentioned before) the error header do not provide a proper HTTP header!? It would also be nice to provide two different error routes: one for client errors (404: not found, forbidden) and another to server errors (HTTP/1.1 500 Server Error).

A suggestion (we've been talking a lot on Respect/Rest) is to implement the URI Template (RFC 6570) for matching routes and hydration of parameters (something macaw lacks but i like using the PHP way of $_GET, $_POST and filter_input()). With a component dealing nicely with URI Templates many projects would benefit from it.

If you want something with more features but still just as simple, check out: http://flightphp.com/

I'm using it to make a JSON backend API and it works great.

http://macaw.co/ Oblivious or on purpose?

Great project. I personally prefer Python over PHP and use it a lot for most of the web applications. But when I must use PHP in some cases, I like frameworks like this.

For precisely this reason, I wrote a PHP router like this called Marg - http://github.com/vaidik/marg. Used it for 3 projects and I love the way I can keep things simple and sane. And that's why I appreciate this project as well.

Great to see sane projects like these in the PHP community.

this is very elegant. i haven't used php (beyond wordpress) in years, so i am sure a lot has changed with all the frameworks which cropped up. one of the things i miss about php was the simplicity of dropping a file into a path and making requests directly to it, no extra dependencies required. i know a lot of people prefer prettier urls, so why not use .htaccess file for mod_rewrite rather than using something like macaw?

nice job on creating a really damn simple interface.

Is there any pattern matching router in PHP? Just like Journey on Rails. It is faster to use Patrern Matching than sequential brute force route.

Magic methods are expensive in PHP. You might as well define those explicitly.

It's... 87 lines of PHP?

I don't see a composer.json in the root of the Github. Is that planned?

Looks like a nice alternative to using Silex if you just need routing.

really nice.

if I had any suggestions at all though it would be to have the 404 route actually return the 404 header (or have a way to specify headers with routes), and also have it handle https.

Double name is double. cf : http://macaw.co/

Handy. Nice