Q: Peter, Last weekend my wife was copying CDs from a friend. She was successful on all of her choices except for Afterglow by Sara M. She did not realize that we were invested in the company that prevented her from burning that CD. After I told her that we had a large position in Sunncomm, she was excited about the technology. Peter, when will the shareholders be rewarded for their patients with Sunncomm? (9/7/2004 8:44:35 AM)
A: Hey, wait a minute. Thats a "when will the share price go up" question in disguise. I dont know for certain, but I believe that as the company continues to add new business and focuses on improving our technology, our value in the marketplace will continue to increase overall. We are working on making it a great year. Lets see how it goes.
Best regards,
Peter
Peter, we the countless masses love your stupendously powerful DRM! We cannot help but spontaneously comment on your awesomeness and the fantastic potential of your company!
Here's to double digit (cents) per share by the end of the year!
As others have pointed out, the NOEXTERNALDATA can't (on it's own) be used to fool the component into loading.
However, it did appear to me that NOEXTERNALDATA along with base64 encoding (or other simple parameter obfuscation) could be used to get around the behaviour for your own controls (just have them decode the obfuscated param values after instantiation).
Of course, the other solution outlined (use a separate client script file and document.write() to emit the and tags) seems even more straightforward.
Developers will have to write some code to get around this either way, but it's not as Chicken Little-esque as some are making it out to be.
Slashdot Mirror
Ah yes, it's the delicious aroma of a well-done web server.
Peter, we the countless masses love your stupendously powerful DRM! We cannot help but spontaneously comment on your awesomeness and the fantastic potential of your company!
Here's to double digit (cents) per share by the end of the year!
Go team go!
With access to the source, the thief could then design exploits and cheats quite easily.
It's not the theft that's the problem: it's the fact that every kiddie in the land possesses the game engine now.
As others have pointed out, the NOEXTERNALDATA can't (on it's own) be used to fool the component into loading.
However, it did appear to me that NOEXTERNALDATA along with base64 encoding (or other simple parameter obfuscation) could be used to get around the behaviour for your own controls (just have them decode the obfuscated param values after instantiation).
Of course, the other solution outlined (use a separate client script file and document.write() to emit the and tags) seems even more straightforward.
Developers will have to write some code to get around this either way, but it's not as Chicken Little-esque as some are making it out to be.