Re: [chromium-dev] Any interest in command line tools for network stack?
One command line tool I have sometimes wanted when debugging, is a way to dump out a cached response from the disk cache. The only way I know to do this currently is create a profile and load it in chrome, then use about:cache to print the response as hex. (At which point you still need to unhexify it and then reverse any filters like bzip2 before you have the content) On Fri, Nov 13, 2009 at 5:46 PM, Wan-Teh Chang w...@google.com wrote: On Fri, Nov 13, 2009 at 11:58 AM, Chris Bentzel cbent...@gmail.com wrote: 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. I also like the idea. These tools can serve as sample code for other projects that are considering taking our network stack. It can also be easier to debug a simple command line tool than a full-blown browser if a network stack bug can be reproduced using a command line tool. Wan-Teh -- 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
Re: [chromium-dev] Any interest in command line tools for network stack?
On Mon, Nov 23, 2009 at 2:26 PM, Eric Roman ero...@chromium.org wrote: One command line tool I have sometimes wanted when debugging, is a way to dump out a cached response from the disk cache. There is a dump_cache.exe utility; it can copy a cache or copy the whole thing to a set of disk files. Only works on windows tho Mike The only way I know to do this currently is create a profile and load it in chrome, then use about:cache to print the response as hex. (At which point you still need to unhexify it and then reverse any filters like bzip2 before you have the content) On Fri, Nov 13, 2009 at 5:46 PM, Wan-Teh Chang w...@google.com wrote: On Fri, Nov 13, 2009 at 11:58 AM, Chris Bentzel cbent...@gmail.com wrote: 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. I also like the idea. These tools can serve as sample code for other projects that are considering taking our network stack. It can also be easier to debug a simple command line tool than a full-blown browser if a network stack bug can be reproduced using a command line tool. Wan-Teh -- 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 -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Any interest in command line tools for network stack?
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
Re: [chromium-dev] Any interest in command line tools for network stack?
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
Re: [chromium-dev] Any interest in command line tools for network stack?
I like the idea. On Fri, Nov 13, 2009 at 11:58 AM, Chris Bentzel cbent...@gmail.com wrote: 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 -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Any interest in command line tools for network stack?
On Fri, Nov 13, 2009 at 11:13 AM, Chris Bentzel cbent...@gmail.com wrote: 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? I'm weakly against the idea, since adding dependencies increases the burden when we want to redesign or update pieces of the network stack. I would change my vote to be in favor if these tools allowed some kind of testing of the stack that is not currently feasible; better testing is always a good goal. PK -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Any interest in command line tools for network stack?
On Fri, Nov 13, 2009 at 12:25 PM, Peter Kasting pkast...@google.com wrote: 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? I'm weakly against the idea, since adding dependencies increases the burden when we want to redesign or update pieces of the network stack. I would change my vote to be in favor if these tools allowed some kind of testing of the stack that is not currently feasible; better testing is always a good goal. I think it would be valuable to have a netcat-like thing implemented using chromium's stack because it would make certain kinds of testing and debugging easier. (In particular, I'm looking at a hang in the ssl tests that only happens in one strange environment, and having a standalone app that just makes an ssl connection using chromium's stack would be quite handy.) -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] Any interest in command line tools for network stack?
On Fri, Nov 13, 2009 at 11:58 AM, Chris Bentzel cbent...@gmail.com wrote: 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. I also like the idea. These tools can serve as sample code for other projects that are considering taking our network stack. It can also be easier to debug a simple command line tool than a full-blown browser if a network stack bug can be reproduced using a command line tool. Wan-Teh -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
