You are trying to deal with these fields: std::vector<unsigned short> text; std::vector<unsigned short> unmodified_text; std::vector<unsigned short> key_identifier;
Right? Is it really the case that those are unbounded in length? Or, is there some small max length that they can be? Maybe 2 or 4 characters is enough? Why isn't this a problem for Windows and Linux since they also have to populate the PlatformKeyboardEvent's m_text, m_unmodifiedText, and m_keyIdentifier fields. If there is no reasonable max length, then we would just have to write ParamTraits<T> classes, and use those to serialize to an IPC::Message as we normally do. But since these events are really just meant to be data, it would be nice to keep the bulk copy if possible. -Darin On Thu, Feb 19, 2009 at 11:30 AM, Avi Drissman <[email protected]> wrote: > Grr. ViewMsg_HandleInputEvent is a real problem. > > Today we bulk-copy raw bytes into the stream (see > RenderWidgetHost::ForwardInputEvent), and that's really not going to work. > What's the preferred approach? Do we create a factory on WebInputEvent so > that we can deserialize at the other end of the pipe, or split the message > for each kind of Web*Event? > > Avi > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
