From: Glyn M. <gly...@gm...> - 2008-08-28 08:00:34
|
Hi Kim, 2008/8/28 Kim Gräsman <kim...@gm...> > Glyn, > > On Thu, Aug 28, 2008 at 09:36, Glyn Matthews <gly...@gm...> > wrote: > > > > In my mind, you send a GET to a server, not the client. When I write > code > > like this I *am* the client, I don't *use* a client. If I'm the only one > > being anal about this then I'll let this point go :) > > I've thought about this too, but substituting "client" for "server" in > the API became really confusing. So maybe "connection" is clearer. On > the other hand, as Dean says, for HTTP 1.0 there is no persistent > connection (as far as I understand it, anyway), only requests. Right, The word "server" is really wrong. > > Then again, thinking about client as a browser, as somebody mentioned, > helps, for me at least. > Yeah, especially as Dean explained that he was attempting to break with convention with this approach. So "server" is wrong, "connection" is misleading, given the explanation elsewhere in this thread, "client" is perhaps the best name that in this context. I can still imagine potential users being confused by this though. Thanks for your input, G |