Do not hang when using stack API in the wrong way. (Trac #8)

[edsiper]

If for some reason a callback misses a final response->end(dr..) call or it do not put the event to sleep, when the callback returns will let the server in an infinite loop.

This do not affect a production environment as is noticed in the development environment, but bother too much trying to kill the service.

Proposed solution: add a new flag into the duda_request_t context specifying if a 'next step or status' have been done. This flag should be modified by response->end(), response->finalize() and response->wait() calls.

Migrated from http://bugs.duda.io/ticket/8

{
    "status": "new", 
    "changetime": "2014-01-02T19:50:33", 
    "description": "If for some reason a callback misses a final response->end(dr..) call or it do not put the event to sleep, when the callback returns will let the server in an infinite loop. \n\nThis do not affect a production environment as is noticed in the development environment, but bother too much trying to kill the service.\n\nProposed solution: add a new flag into the duda_request_t context specifying if a 'next step or status' have been done. This flag should be modified by response->end(), response->finalize() and response->wait() calls.", 
    "reporter": "edsiper", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1388692233461102", 
    "component": "API", 
    "summary": "Do not hang when using stack API in the wrong way.", 
    "priority": "major", 
    "keywords": "", 
    "version": "", 
    "time": "2014-01-02T19:50:33", 
    "milestone": "", 
    "owner": "edsiper", 
    "type": "defect"
}