I'm using them as a learning exercise for the network stack - and I'm guessing that they will help debug behavior in the future as well.
I don't intend to add additional functionality over the standard tools - in fact, I promise you they'll be less functional than the standard tools. For example, my hresolv executable just takes a hostname and a port as options for now. I'll spend a bit more time getting them to a reasonable point and send a patch out for review - figure decision will be easier then over a vague description. Thanks, Chris On Fri, Nov 13, 2009 at 2:49 PM, Jeremy Orlow <jor...@chromium.org> wrote: > What's the intended purpose of such tools? Do they offer any functionality > beyond the standard tools? Do you envision them being helpful to people > debugging the Chromium network stack? > (Me replying does in no way imply that I have the authority to say yes or > no, btw. :-) > > On Fri, Nov 13, 2009 at 11:13 AM, Chris Bentzel <cbent...@gmail.com> wrote: >> >> Howdy, >> >> I've been trying to dive into the Chromium codebase and have been >> focusing on the network stack after getting the gist of how Chromium >> on the whole is organized. >> >> I've written a few hacky little command line tools to exercise some of >> the networking components (nslookup-like for HostResolver, wget-like >> for HttpNetworkTransaction). Should I spend time trying to flesh these >> out and add to net/tools, or is this something which doesn't belong in >> the chromium codebase? >> >> Thanks, >> Chris >> >> -- >> Chromium Developers mailing list: chromium-dev@googlegroups.com >> View archives, change email options, or unsubscribe: >> http://groups.google.com/group/chromium-dev > > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
