diff options
| author |   Marcel Saegebarth <marc@mos6581.de> | 2015-02-06 20:35:55 +0700 |
|---|---|---|
| committer |   Willy Sudiarto Raharjo <willysr@slackbuilds.org> | 2015-02-07 04:58:57 +0700 |
| commit | fdec5f2d1870e2f8f8a598500125a829ded2157a (patch) | |
| tree | 8f200a9ee12dba7255bfa0f290ca8a675cb0fc93 /libraries/libevhtp/README | |
| parent | 8e345cefbe19d133e041bd99e469ce3d044ea7dc (diff) | |
| download | slackbuilds-fdec5f2d1870e2f8f8a598500125a829ded2157a.tar.gz slackbuilds-fdec5f2d1870e2f8f8a598500125a829ded2157a.tar.xz | |
libraries/libevhtp: Added (libevent HTTP API).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'libraries/libevhtp/README')
| -rw-r--r-- | libraries/libevhtp/README | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/libraries/libevhtp/README b/libraries/libevhtp/README new file mode 100644 index 0000000000..55083d94c6 --- /dev/null +++ b/libraries/libevhtp/README @@ -0,0 +1,7 @@ +Libevhtp was created as a replacement API for Libevent's current HTTP +API. The reality of libevent's http interface is that it was created +as a JIT server, meaning the developer never thought of it being used +for creating a full-fledged HTTP service. Infact I am under the +impression that the libevent http API was designed almost as an +example of what you can do with libevent. It's not Apache in a box, +but more and more developers are attempting to use it as so. |