On Wed, Oct 14, 2009 at 3:50 PM, Adam Barth <[email protected]> wrote:
> On Wed, Oct 14, 2009 at 2:48 PM, Michael Nordman <[email protected]> > wrote: > > As mentioned f2f, this falls apart as soon as Chrome tries to manufacture > a > > security origin. I'm not sure, may already have instances of that in the > > code base for all I know. > > I'm not sure Chrome is smart enough to manufacture a SecurityOrigin. > There's a lot of tricky work in the canonicalization that we don't > want to duplicate. > > Adam > Agreed, and we shouldn't be in that business. I think for all our use cases, the factory for security origins can be WebCore. Chrome just needs to be able to serialize / de-serialize a security origin, compare them, and possibly access some component parts (though I'm not certain of this requirement). -Darin --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
