So why do they need to send a "dvd player cookie"?
Cookies are for associating HTTP requests, which are stateless by nature, to create the notion of a "session". For the purpose of getting DVD and CD data from their handy-dandy server, I see no need to create a session any more than there is a need for doubleclick.com to send a cookie when my browser GETs a banner ad.
Note that Mr. Caulton from Microsoft said they "are not" using the information they collect for "marketing purposes," etc. He did not say they "can not," or even that they "would not." He simply said they would change their privacy policy. Well, they can change their privacy policy again if they want to, and they can start using this uneeded cookie for anything they want.
I'll say it again, if they didn't want or need to associate multiple separate HTTP requests with a single user, then they don't need a cookie.
If they really don't want to track, then they should stop sending a cookie.
Notice they're offering "free" tools to help you determine if you're infected - just fill out this form with all of your contact information (all fields are required.)
These guys came out of nowhere, want to make a splash, and collect a list of potential customers in the process.
Notice that MICROS~ waxed at length about all the good reasons for the new rules, but they didn't say one word about why the NT4 certifications will expire.
Of course I think we all know why they want NT4 to expire. This is just a way to leverage another one of their monopolies (MCSE exams) to promote the sales of their great new OS. It's all about the leverage.
Although it's not clear exactly which Y2K method is being discussed here, it appears it's the basic "windowing", "cusp date", or "epoch date" technique.
This is so old, there's prior art everywhere. I'm enough of a dinosaur that I used the technique back in the late 70's, and it was common practice. (Er, that's the 1970's, not the 2070's. Oh shit, I just used windowing, they're after me.)
Slashdot Mirror
The asshat is the one that doesn't know the difference between "development cost" and "manufacturing cost" and calls someone an asshat.
Insightful? Get real. The proffit far outstrips the development cost. Just look at their bank account. What a toadie.
So even though you only list three options for the orgin of the code, your subsequent paragraph adds a fourth, even more likely possibility:
4. SCO's code comes directly from Linux.
Cookies are for associating HTTP requests, which are stateless by nature, to create the notion of a "session". For the purpose of getting DVD and CD data from their handy-dandy server, I see no need to create a session any more than there is a need for doubleclick.com to send a cookie when my browser GETs a banner ad.
Note that Mr. Caulton from Microsoft said they "are not" using the information they collect for "marketing purposes," etc. He did not say they "can not," or even that they "would not." He simply said they would change their privacy policy. Well, they can change their privacy policy again if they want to, and they can start using this uneeded cookie for anything they want.
I'll say it again, if they didn't want or need to associate multiple separate HTTP requests with a single user, then they don't need a cookie. If they really don't want to track, then they should stop sending a cookie.
-hans
These guys came out of nowhere, want to make a splash, and collect a list of potential customers in the process.
Of course I think we all know why they want NT4 to expire. This is just a way to leverage another one of their monopolies (MCSE exams) to promote the sales of their great new OS. It's all about the leverage.
This is so old, there's prior art everywhere. I'm enough of a dinosaur that I used the technique back in the late 70's, and it was common practice. (Er, that's the 1970's, not the 2070's. Oh shit, I just used windowing, they're after me.)
-ac