On Fri, Dec 18, 2009 at 8:57 AM, Sergio Tudela Romero <
sergiotudelarom...@gmail.com> wrote:
> The fact is that every time a cookie is saved the "key" to this is the
> domain where it was created (is this the problme for me). Thus I could
> never have 2 cookies in a single domain since both have the same
> "key".
>
No, cookies have names, and a cookie's key is the host + cookie name pair.
This is how websites set many cookies at once.
In other: 1 domain with several different cookies differences with the
> "key" the process id of that tab... using a single cookies store that
> offers the profile of this render.
>
Process IDs change every time you close and reopen a tab, or close and
restart the browser. If we have cookies linked to PIDs 1, 2, and 3, and you
close 2 and 3, then open a new tab 4 on the same site, then close the whole
browser and start anew, what are the cookies at each stage? It's impossible
to know what to do.
1 Render - 1 profile - 1 storage of cookies - 1 cookie per domain (the
> key of the cookie is the domain).
>
No, n cookies per domain.
1 Render - 1 profile - 1 storage of cookies - N cookies for 1 domain
> (the key of the cookie is the process id of the tab).
>
If you have one renderer, you only have one PID, so you don't have n cookies
for n PIDs.
It's best to attack problems by first stating a use case, then looking for
solutions. It's not clear what use case you're solving.
PK
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
