Sean Landis <sean.landis <at> gmail.com> writes: > > Jerome Louvel <contact <at> noelios.com> writes: > > Hi all, > > > > Thanks for the quality of the feed-back. I feel like I'm now grasping all > > aspects of the problem and can propose a solution: > > > > 1) Split the Resource class into an abstract Handler class and a Resource > > subclass > > Hi Jerome, > > What is the motivation of the Handler class? I have no problem with it, > I just want to understand. Is it merely to be explicit about lower level > API and higher level, or is there more to it?
So what's the difference between a Handler and a Finder? The flow of the request would go through the following after this refactoring. Server -> Component -> Application -> Router -> Finder -> Handler -> Resource -> Domain Object I'm trying to understand the separation-of-concern/value-add that each layer offers. Thanks. Sumit
