On Thu, Jun 18, 2009 at 2:11 PM, Philippe Vaucher<philippe.vaucher@gmail.com> wrote:
* The #1 feature should be supporting http 1.1 well (also https). Many libaries provide a http 1.0 implementation but fail short of supporting the many options http provides (I know this is a huge undertaking!) . At this point I don't see the value of supporting file (or planning to support ftp).
Sometimes I need to use them :) Seriously though, the power of working with URLs is their polymorphism, so the more protocols the better IMHO.
While I totally agree with that, I just want to point out that the discussion wether this library should support more protocols than HTTP raise a fundamental design issue: if you start to make it support more protocols, then you'll end with something like libcurl (which is a very nice library), and if that's the case it might be simpler to write a boost libcurl wrapper (the current c++ wrapper of libcurl aren't very nicely designed).
thanks, this is exactly the point I was trying to make but much better explained!