From: K. G. <kim...@gm...> - 2008-10-07 08:47:30
|
Hi Glyn, On Tue, Oct 7, 2008 at 10:19, Glyn Matthews <gly...@gm...> wrote: > >> For what it's worth, I've been experimenting with getting the uri >> separated out of the request, but the more I look at it, the less >> value I think it brings... > > Have you committed any code? Nope, not yet. > What do you mean by "less value"? IMO it > makes sense to separate the URI from the request, but I haven't given much > thought to the details. Looking at it again, maybe it isn't so bad :) I think I was having problems with the different shapes of different types of URIs, and that each scheme should probably be represented by its own class. I'm not sure, for example, what the HTTP client should do if it's presented with an FTP URL. And does it make sense to send a string to to the HTTP client? Maybe it should be a 'uri' or maybe it should be an 'http_uri'? > Is it just difficult to do or do you just not think > its worth it by design? I definitely think it's worth doing, I'm just not sure I can find a good abstraction at the moment, but we could start with a simple URI and move from there, I suppose. - Kim |