[
https://issues.apache.org/jira/browse/DEFT-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Schildmeijer updated DEFT-165:
------------------------------------
Priority: Major (was: Trivial)
Description:
org.deftserver.web.http.HttpRequest#setIOLoop is never used. This should be
invoked by the framework (method is protected) after the HttpRequest is created.
"The reason for this is so that a user defined RequestHandler will have access
to its surrounding IOLoop. (In a single threaded environment its sufficient to
use the IOLoop.INSTANCE if you need the ioloop, e.g. for adding timeouts,
callback or a new IOHandler)."
was:The IOLoop field is unnused (unuse getter/setter)
Issue Type: Bug (was: Improvement)
Summary: Not injecting the IOLoop into each HttpRequest (was:
Unncessary IOLoop field in HttpRequest)
> Not injecting the IOLoop into each HttpRequest
> ----------------------------------------------
>
> Key: DEFT-165
> URL: https://issues.apache.org/jira/browse/DEFT-165
> Project: Deft
> Issue Type: Bug
> Reporter: Roger Schildmeijer
>
> org.deftserver.web.http.HttpRequest#setIOLoop is never used. This should be
> invoked by the framework (method is protected) after the HttpRequest is
> created.
> "The reason for this is so that a user defined RequestHandler will have
> access to its surrounding IOLoop. (In a single threaded environment its
> sufficient to use the IOLoop.INSTANCE if you need the ioloop, e.g. for adding
> timeouts, callback or a new IOHandler)."
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
