Comment on Raphters, a web framework for CparentComments−tptacek15yThe downside to doing evhttp is that he'll have to write his own request parsing (I think he's relying on Apache/CGI to do that for him now).But if you're going to do a C web framework (and... really? you sure about that?), that's probably how you should do it.−sigil15y> The downside to doing evhttp is that he'll have to write his own request parsing...Which, these days, isn't a huge deal. Both of these are decent:https://github.com/ry/http-parserhttps://github.com/mongrel/mongrel/blob/master/ext/http11/ht...−DanWaterworthOP15yRequest parsing is no big deal, I've already written a json parser/generator for this project (though it's in a separate project atm).
Comments
The downside to doing evhttp is that he'll have to write his own request parsing (I think he's relying on Apache/CGI to do that for him now).
But if you're going to do a C web framework (and... really? you sure about that?), that's probably how you should do it.
> The downside to doing evhttp is that he'll have to write his own request parsing...
Which, these days, isn't a huge deal. Both of these are decent:
https://github.com/ry/http-parser
https://github.com/mongrel/mongrel/blob/master/ext/http11/ht...
Request parsing is no big deal, I've already written a json parser/generator for this project (though it's in a separate project atm).