MobileRead Forums - View Single Post

wwang · 06-20-2005, 08:49 AM

I know we SHOULD not, but I know that for many slow sites, I can and do open multiple windows to the same sometimes slow sites. I don't see how this is much different... I know the site is waiting or doing other processing that I am not going to overload it by doing an outrageous amount of connections. Just something more then 2 to get around a limitation in the plucker code problem listed above in this same thread.

I know before we had sunrise, we had multiple threads for the same file, and there was a WAY I could get more then 4, it may have been a bug, but there still was a way. Might you share same exploit for those of who might be running into a problem? I know that the server is not competely busy and eventually I know there are many files I am not going to be requesting because the files are not local to the remote host so I will not be downloading many of the embedded files.

I also don't see the difference between having multiple windows open to the same server , say 3 documents x 2 threads = 6 connections, or 2 documents x 3 threads = 6 connections...

I know that no matter what you do, if you overload the server too much, you are not going to get the data any faster! :-)

06-20-2005, 08:49 AM	#6
wwang Connoisseur Posts: 62 Karma: 10 Join Date: Jun 2005 Location: California, USA Device: Palm TX SmartQ 7	http spec for multiple connections... I know we SHOULD not, but I know that for many slow sites, I can and do open multiple windows to the same sometimes slow sites. I don't see how this is much different... I know the site is waiting or doing other processing that I am not going to overload it by doing an outrageous amount of connections. Just something more then 2 to get around a limitation in the plucker code problem listed above in this same thread. I know before we had sunrise, we had multiple threads for the same file, and there was a WAY I could get more then 4, it may have been a bug, but there still was a way. Might you share same exploit for those of who might be running into a problem? I know that the server is not competely busy and eventually I know there are many files I am not going to be requesting because the files are not local to the remote host so I will not be downloading many of the embedded files. I also don't see the difference between having multiple windows open to the same server , say 3 documents x 2 threads = 6 connections, or 2 documents x 3 threads = 6 connections... I know that no matter what you do, if you overload the server too much, you are not going to get the data any faster! :-)