On Fri, Jul 10, 2009 at 5:04 PM, Jeremy Orlow<[email protected]> wrote: > WebCore::String has the interesting property of differentiating between an > empty string and a null string. In string16, however, there is no such thing > as null. > The LocalStorage implementation I'm working on proxies data between the > rednerer processes and browser process. Some of this data is in the form of > WebCore::Strings that need to differentiate between empty and null. > I could add a boolean to all IPC messages where the string could be null and > then add explicit checking (rather than using the elegant and implicit type > conversions that normally happen from WebCore::String <-> WebKit::WebString > <-> base::string16) but that seems pretty ugly. I think a better solution is > adding a new type to base, adding serializing code to > common/ipc_message_utils, and adding implicit type conversions between > WebKit::WebString and this new type. > First of all, is that a good idea? Second of all, what would be a good name > for it? NullableString16?
What is happening with Darin's WebCore interface stuff. I remember he was planning on having some kind of WebString that could be passed to IPC. Is this still the case, and can we use that instead? Brett --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
