utak3r
31st May 2008, 11:38 AM
Attention all the ROM cookers!
If you were ever considering incorporating Opera Mini into your ROM (making an OEM package) - DON'T! At least, don't do it in a state after generating random data.
Why? Opera Mini works through a cache. A server-side cache... and cached data are assigned to an unique ID of the particular browser instance. The problem is, that cooked-in Opera Mini into ROM gives all its users the same unique ID... Now, if one of the users will login into some site, and another user will enter this same site.... well, he'll be logged in.
So.... either do not cook it in, or - do it in a state as it is just right after installation, before its first run!
If you were ever considering incorporating Opera Mini into your ROM (making an OEM package) - DON'T! At least, don't do it in a state after generating random data.
Why? Opera Mini works through a cache. A server-side cache... and cached data are assigned to an unique ID of the particular browser instance. The problem is, that cooked-in Opera Mini into ROM gives all its users the same unique ID... Now, if one of the users will login into some site, and another user will enter this same site.... well, he'll be logged in.
So.... either do not cook it in, or - do it in a state as it is just right after installation, before its first run!