Although I agree with the fact that this is not a very nice thing, trojanized computers, spam relays etc. The DNS itself is not doing anything illegal, a dynamic DNS with a round-robin which updates every 5 minutes is not illegal in itself. You can't block a DNS because it does something inventive within the boundries set by the Although I know that dynamic IPs for primary and secondary nameservers are not allowed in a number of countries, they are required to be static in the Netherlands and afaik Belgium. And afaik they are absolutely not allowed to be CNAME'd. I think this is more a case of bad practise on the part of the root domain provider, if they allow people to do things like this, then this is result.
This is absolutely true. You can actually use all the buffer/cache of all the routers, switches and computers allocate you in the way of the package to store data. About 4 years ago I did a test transfering approx 50 Mb of data, as an icmp payload, taking a long route (satelite/trans-atlantic route etc). My main problem with it, even with the cache, translation and bouncing delay, was that I was getting the first packets back by the time I was sending packet #. (My PoC wasn't very efficient.)
I still think it's a cool idea though, just have to make sure that you use Reed-Solomon (or such) so you can reconstruct any dropped packets.
I was looking over the site and a number of things concerned me.
Firstly the choice of Java, personally I have no gripe about this. And reading that a choice was made to use language-independent formats is a good idea. My main concern is for the larger scaling and distribution over multiple machines. At present I make the educated guess that a project on this scale, in Java, would still be best run on a `hardware base as uniform as possible', like UltraSparc 450's with a fibre back-plain.
My second concern is that there is so much choice of indexing and searching technique that there are sure to be some problem due to Patent restrictions. Just browsing the US patent office gave me a couple of possible Patent nasties; 6,463,428 or 6,278,992. (And about 10 others I glanced at...)
Lastly DB, in the short time I've been looking at the code it seems to me that a choice was made to implement a DB build for the problem. Although this could be a good thing, it is usually better to reuse existing products. I found SleepyCat (DB4) to match the requirements. And if the choice is final read this. [1]
I hope these comments are useful to somebody at least.
Slashdot Mirror
Although I agree with the fact that this is not a very nice thing, trojanized computers, spam relays etc. The DNS itself is not doing anything illegal, a dynamic DNS with a round-robin which updates every 5 minutes is not illegal in itself. You can't block a DNS because it does something inventive within the boundries set by the
Although I know that dynamic IPs for primary and secondary nameservers are not allowed in a number of countries, they are required to be static in the Netherlands and afaik Belgium. And afaik they are absolutely not allowed to be CNAME'd.
I think this is more a case of bad practise on the part of the root domain provider, if they allow people to do things like this, then this is result.
I could rant, but won't.
This is absolutely true. You can actually use all the buffer/cache of all the routers, switches and computers allocate you in the way of the package to store data.
About 4 years ago I did a test transfering approx 50 Mb of data, as an icmp payload, taking a long route (satelite/trans-atlantic route etc).
My main problem with it, even with the cache, translation and bouncing delay, was that I was getting the first packets back by the time I was sending packet #. (My PoC wasn't very efficient.)
I still think it's a cool idea though, just have to make sure that you use Reed-Solomon (or such) so you can reconstruct any dropped packets.
I was looking over the site and a number of things concerned me.
Firstly the choice of Java, personally I have no gripe about this. And reading that a choice was made to use language-independent formats is a good idea. My main concern is for the larger scaling and distribution over multiple machines.
At present I make the educated guess that a project on this scale, in Java, would still be best run on a `hardware base as uniform as possible', like UltraSparc 450's with a fibre back-plain.
My second concern is that there is so much choice of indexing and searching technique that there are sure to be some problem due to Patent restrictions.
Just browsing the US patent office gave me a couple of possible Patent nasties;
6,463,428 or 6,278,992. (And about 10 others I glanced at...)
Lastly DB, in the short time I've been looking at the code it seems to me that a choice was made to implement a DB build for the problem. Although this could be a good thing, it is usually better to reuse existing products. I found SleepyCat (DB4) to match the requirements. And if the choice is final read this. [1]
I hope these comments are useful to somebody at least.
[1] http://www.xlnt-software.com/xml_dl.html
did you just type 'gzip -cd patchXX.gz | patch -p0"???