Implemented Single threaded Dispatcher,wrote test cases

I've implemented single thread dispatcher. If this is correct then I'll update it to concurrent version which I've started. I just wanted to confirm my approach.
1. Parse and create request is done by Adapter. I'm just initiating that functionality by calling Adapter function. In many implementations that I saw for reference,HTTPRequest is getting generated by Processor. I choose to delegate that functionality to Dispatcher because,I want my dispatcher to deliver incoming requests to specific handler which is intended to handle it. In our case right now,we are just handling static requests so it may no make more sense but when we will introduce dynamic handlers,at that time it will make sense(my view of thinking) .and If I do not create HTTPRequest object in dispatcher then I have to go through Connection data to check extension of requested file and then decide to whom I should deliver request for processing. Thats why I'm creating HTTPRequest by calling Adapter's method.
2.Create mapper and configure it can be done after specific time interval. I haven't done that yet. What I've thought of is I'll call that function after certain amount of time. e.g say after every 10 seconds I want to refresh my mapper to insure that it will respond for changes in Handle.config file.
3.Handle the discovery of the request handler based on the request. If this should not be done in dispatcher then why we are introducing one more component in between which will just take data input from one end and will give it to the other.. I know that is to free the listener as soon as possible to listen further requests. But if we are introducing one component in between then if we add some intelligence inside that which will decrease processing of further components then that make more sense in adding Dispatcher in between... Again as per my point of view....