Quote:
Originally Posted by BigFurry
Sounds like a good idea to me! Even if just as a backup next to cookies. Because of the clearing cookies / private browsing stuff that you mentioned.
The limited cookie space is not a big issue in my opinion. If a big aggregator like CCBILL *knows* that the limit *could* be reached, they should just improve their system. They could stop adding individual cookies for each website visited, and identify the visitor with one Id. One cookie identifies a visitor, eg. ccbillVisitorProfileId.
The rest of the information connected to this visitor can be stored on their server (ie. for 57 CCBILL sites visited, 57 Website-ActiveAffiliateId-Expirations stored.)
But maybe they already do this by now, I have no idea.  |
Yep you would think that would be the way to go but the problem with that approach is the load on the server end.
If youve got say 100,000 users visiting say 1,000 ccbill affiliate websites then thats already 100 million bits of data you have to store on the back end server. Almost all of which is going to be unused unless the user actually joins a site
Obviosuly with cookies all that workload is placed on the client end