From 85b434ffc8870a592044b29686f6d2f352fe7c45 Mon Sep 17 00:00:00 2001 From: Trygve Laugstøl Date: Thu, 4 Jul 2013 18:53:30 +0200 Subject: o Initial import of my PostgreSQL background worker + HTTP experiment. --- README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 README.md (limited to 'README.md') diff --git a/README.md b/README.md new file mode 100644 index 0000000..fa3b02b --- /dev/null +++ b/README.md @@ -0,0 +1,15 @@ +This is me mainly scratching an itch, but it is a small proof of +concept on how possible it is to embed a HTTP server into PostgreSQL +as a background worker. + +Right now it uses libebb as an event-driven HTTP server. As the +background workers only have a single connection to the database, one +process can only serve one client at a time. Libebb support multiple +connection, you better not connect multiple times. + +Other possible HTTP implementations: + + * https://github.com/valenok/mongoose.git - tried it, got complicated + because it wanted to control forking. + * https://github.com/joyent/http-parser - a plain HTTP parser, might + be useful if I end up with a custom HTTP server. -- cgit v1.2.3