Probably 3 million pages, not sites.
According to Russians (http://info.nic.ru/st/38/out_1362.shtml) there were 7897 domain names registered in.su TLD by 11/26/2006. And looks like they aren't going to give it up for nothing -.su domain is $100/year.
Sometimes it can save your life
on
Hijacking .NET
·
· Score: 1
Dan's example illustrates nothing indeed. Isn't it stupid to rely on private methods when robust solution may take just days. Write it once and forget about it.
But sometimes such hijacking might be worth doing. Here is the story. There is really painful (wellknown and confirmed) bug in.NET XSLT implementation (in both frameworks 1.0 and 1.1): one cannot return a nodeset from an extenstion function, because XSLT impl expects an instance of one of *internal* class! It's not private, just internal, but anyway how can you return it?
So, once you can instantiate internal class by reflection (and security permits that in your environment) you can workaround it. Of course it won't work probably in the next framework version, but who cares - it's bug's workaround - if bug will be fixed there will be no more need to hijack.
Slashdot Mirror
Probably 3 million pages, not sites. According to Russians (http://info.nic.ru/st/38/out_1362.shtml) there were 7897 domain names registered in .su TLD by 11/26/2006. And looks like they aren't going to give it up for nothing - .su domain is $100/year.
Dan's example illustrates nothing indeed. Isn't it stupid to rely on private methods when robust solution may take just days. Write it once and forget about it.
But sometimes such hijacking might be worth doing. Here is the story. There is really painful (wellknown and confirmed) bug in .NET XSLT implementation (in both frameworks 1.0 and 1.1): one cannot return a nodeset from an extenstion function, because XSLT impl expects an instance of one of *internal* class! It's not private, just internal, but anyway how can you return it?
So, once you can instantiate internal class by reflection (and security permits that in your environment) you can workaround it. Of course it won't work probably in the next framework version, but who cares - it's bug's workaround - if bug will be fixed there will be no more need to hijack.
More details about this particular hijacking case at On returning nodeset from XSLT extension function in .NET.