The Mongrel2 web server works this way. It converts HTTP requests into
ZeroMQ messages that handlers can process asynchronously. I'd say it's a
legitimate approach. :)
On Tue, Dec 30, 2014, at 12:24 PM, sam pendleton wrote:
if it's a request for a page, maybe that page should be cached by the
web server and served
but what if it's something like a POST request
does it make sense for an app to create a new job for each http POST
request on a certain endpoint or should the endpoint process the
request immediately?
by immediately, i mean use a few function calls to validate the data,
insert the data, and on success or failure of updating the db, return
this status to the user
i can do this with 3-4 lines, but i can't decide if i should just
throw the request into a job scheduler
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
