: Whereas the XmlUpdateRequestHandler handles its whole request within a : single class, the CSVRequestHandler delegates almost all of its : implementation to a CSVLoader class. Is there a short answer to why : there would be a split in one case and not the other? (I guess I'm
Off the cuff: I *think* it was just an issue of simplifying state management. RequestHandler's have to be thread safe and process concurrent handleRequest calls. In XmlUpdateRequestHandler this was done using local variables in the method ... whereas in CSVRequestHandler it was simpler to construct a new CSVLoader to process each request (which didn't need to be threadsafe) But take all of this with a grain of salt, because i wasn't involved with thatcode at all, it's just the explanation that makes the most sense to me now that you ask. (I believe the XmlResponseWriter works fairly similarly) -Hoss
