search

moutard / SubZoom-Proto1

1 stars 1 forks source link

New RefererID #3

Closed fwouts closed 12 years ago

HadrienR commented 12 years ago

So, the point is simply to be able to identify with the new ReferID where a new tab comes from (what URL).

Is it not clear or is the challenge harder than expected?

fwouts commented 12 years ago

Neither. I just copy-pasted my todos from the Google Doc to here in order to have a better history of changes. Working on it now :)

HadrienR commented 12 years ago

Cool, may the force be with you!

fwouts commented 12 years ago

We're May 12th, not May 4th ;)

HadrienR commented 12 years ago

Then... May the 12th be with you, young Padawouts.

fwouts commented 12 years ago

Alright so I got some code ready, but I need some help from @moutard here. I think there is no actual code linking Chrome's visitId to the VisitItem. There is some old code, but it doesn't seem to match (sometimes it's called _sChromeId, sometimes _sChromeVisitId). Should we clean this up?

moutard commented 12 years ago

Hi,

Actually for the moment I don't use _sChromeId, and _sChromeVisitId. But we use our own database id. (Those id are supposed to ba able to sync our database with chrome's database) but only on the future. Can you create a new refer id using our own id ?

fwouts commented 12 years ago

Oh okay, I didn't get that. Will do :)

moutard commented 12 years ago

Long term issue. And fwouts is not here anymore so I close this issue. To make some clean.