summaryrefslogtreecommitdiffstats
path: root/third_party/libevent
diff options
context:
space:
mode:
authorpkasting@chromium.org <pkasting@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-09-15 21:17:32 +0000
committerpkasting@chromium.org <pkasting@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-09-15 21:17:32 +0000
commite688d9c126f890cdb361e537463265ff6345cd8d (patch)
tree4e02e48c0357cc5c2b322dbb71796c2c87c853c9 /third_party/libevent
parent5d391c8d58c770e35379ce475b1831cab6e79799 (diff)
downloadchromium_src-e688d9c126f890cdb361e537463265ff6345cd8d.zip
chromium_src-e688d9c126f890cdb361e537463265ff6345cd8d.tar.gz
chromium_src-e688d9c126f890cdb361e537463265ff6345cd8d.tar.bz2
Fourth attempt at the following. Unreviewed, this was originally reviewed in http://codereview.chromium.org/7550002 .
Clean up SSL false start blacklist code. Numerous changes, including: * Handle trailing dots in LastTwoLabels() as in http://codereview.chromium.org/7518035/ . Rename this function to LastTwoComponents() to match the terminology used in the RegistryControlledDomainService and elsewhere in Chrome. * Since callers are using std::string anyway, make the functions in the header take const std::string& instead of char*. This also allows doing string operations on them. * Use string operations (like find_last_of()) in place of hand-written algorithms, for brevity, clarity, and safety. * Avoid "unsigned", which the style guide forbids, and use allowed types like size_t, uint32, or int (depending on the situation). * Avoid #define and "using". * Use standard algorithms for similar reasons as using string ops. * Use file_util functions to significantly abbreviate file reading/writing code. * Use wmain() (on Windows) in combination with FilePath to avoid issues if the provided pathname has extended characters that don't flatten losslessly to the default codepage (thanks Darin for pointing out this issue). * Avoid casting where possible. Avoid some casts for printf()-style calls by using a string stream, which also allows for slightly less boilerplate. * Convert non-error uses of stderr to the chrome-standard VLOG(1). * Correctly handle hostnames with trailing dots in the input file. * In general, shorten code where possible. Because this adds a dependency on base, and ssl_false_start_blacklist_process has the "#host" specifier in net.gyp, bradnelson tells me that base and its dependencies need an explicit "host, target" toolchain list for the Linux builds to work correctly. It would be nice if we could avoid this but I guess gyp would have to be smarter or something. BUG=none TEST=none Review URL: http://codereview.chromium.org/7903016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@101378 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/libevent')
-rw-r--r--third_party/libevent/libevent.gyp1
1 files changed, 1 insertions, 0 deletions
diff --git a/third_party/libevent/libevent.gyp b/third_party/libevent/libevent.gyp
index f4c9be0..55b19cd 100644
--- a/third_party/libevent/libevent.gyp
+++ b/third_party/libevent/libevent.gyp
@@ -13,6 +13,7 @@
'target_name': 'libevent',
'product_name': 'event',
'type': 'static_library',
+ 'toolsets': ['host', 'target'],
'sources': [
'buffer.c',
'evbuffer.c',