huge wnpp bug report page
Hi, I tried to take a look at the wnpp bug page but neither Konqueror nor Firefox were able to handle it on my system. 3182462 bytes for the HTML code of a single web page is a bit much, isn't it? So I was just wondering if it is really necessary to show 3500 resolved issues by default? They could be moved to a different page. Additionally, all links contain the server name. Why? Using a href=bugreport.cgi?bug=123456/a would be enough and would save a lot regarding download size. All the http://bugs.debian.org/cgi-bin/; prefixes could be ommitted. This would reduce page size by 93 bytes per bug ( 500KB total). I hope that something can be done about this to make the BTS web pages more usable. HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: huge wnpp bug report page
Hendrik Sattler wrote: I hope that something can be done about this to make the BTS web pages more usable. Are you perhaps not aware of the much smaller indices into the BTS here? http://www.debian.org/devel/wnpp/ Ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: huge wnpp bug report page
Hi, I tried to take a look at the wnpp bug page but neither Konqueror nor Firefox were able to handle it on my system. Really? Galeon handles it fine, as does Firefox (the latter on win32). 3182462 bytes for the HTML code of a single web page is a bit much, isn't it? Possibly. It's also 25% greater than the size of the page you quoted (wgetting the page gives an output of 2634857 bytes). Additionally, all links contain the server name. Why? Using a href=bugreport.cgi?bug=123456/a would be enough and would save a lot regarding download size. All the http://bugs.debian.org/cgi-bin/; prefixes could be ommitted. This would reduce page size by 93 bytes per bug ( 500KB total). Erm... no, they don't. For instance, having a copy of ftp.d.o's bug page handy :) : lia href=bugreport.cgi?bug=271782#271782: udeb sources need to be in sarge/a brPackage: a class=submitter href=pkgreport.cgi?pkg=ftp.debian.orgftp.debian.org/a; Severity: emimportant/em; Reported by: a class=submitter href=[EMAIL PROTECTED]Goswin von Brederlow lt;[EMAIL PROTECTED]gt;/a; Tags: strongsarge/strong; strong1 year and 323 days old/strong. Cheers, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: huge wnpp bug report page
Am Freitag 04 August 2006 13:49 schrieb Ben Armstrong: Hendrik Sattler wrote: I hope that something can be done about this to make the BTS web pages more usable. Are you perhaps not aware of the much smaller indices into the BTS here? http://www.debian.org/devel/wnpp/ Indeed, didn't know it, yet. And much better :) HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: huge wnpp bug report page
Hi, Am Freitag 04 August 2006 13:39 schrieb Adam D. Barratt: I tried to take a look at the wnpp bug page but neither Konqueror nor Firefox were able to handle it on my system. Really? Galeon handles it fine, as does Firefox (the latter on win32). Really. Firefox gets very slow, konqueror needs ages to load the page (over a DSL line) and somewhere in between doesn't respond anymore. 3182462 bytes for the HTML code of a single web page is a bit much, isn't Possibly. It's also 25% greater than the size of the page you quoted (wgetting the page gives an output of 2634857 bytes). Maybe, I looked at the code from firefox, maybe it made them absolute automatically (it didn't ask if it should :-( ). Still, 2.5MB pure text+html is way too much. HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
