From: Austin Ziegler Date: 2004-08-22T12:16:17+09:00 Subject: Re: Idea: Webshare On Sun, 22 Aug 2004 06:19:08 +0900, Patrick May wrote: > P.S. About the only cgi design suggestion I see on ruby-talk > that I outright disagree with is Request / Response. > > I experimented with this in Narf, and I think it is a mistake. You end > up with two objects, with alot of shared implementation code, that > always go together, split apart for no practical reason. I don't mind > having Request / Response separated in the documentation, but splitting > it in the code just adds typing. When will you ever want a request > without the response? Martin Fowler has a name for this refactoring, > but I don't have his book. As someone who thinks that a request/response is a good thing, I'll first agree with Andreas that while they may share implementations, they don't share data (which suggests a Request class, a Response class, and a "Message" class). Separating request and response, to me, is as simple as the splitting of STDIN, STDOUT, and STDERR. In theory, I could choose to request from one computer but respond in a different location -- why should I be restricted to responding to the person who made the request? (Granted, I can't see why I would do such a thing, but who knows whether such a feature would be useful?) -austin -- Austin Ziegler * halostatue@gmail.com * Alternate: austin@halostatue.ca