KURLGoogle's pre-parsed canonicalSpec constructor should take a CString Internally it allocates a CString, so this would not be a significant change for any existing code. This change would allow us to efficiently copy from KURL -> CString -> KURL since CString is internally reference counted. I plan to leverage this in our WebKit layer.
Created attachment 27643 [details] v1 patch This patch was already reviewed by Brett Wilson (the author of KURLGoogle) here: http://codereview.chromium.org/21343
Comment on attachment 27643 [details] v1 patch Looks fine to me. I much prefer CString over char* + len anyway!
http://trac.webkit.org/changeset/40981