#12 Torrent peer table incomplete

[Charles Parker]

Hi,

I've noticed that when using ctcs to view the details of a torrent, the table that contains the list of peers is quite often incomplete. By this I mean that I don't think ctcs is sending all of the html it intended to. Here are some symptoms that I've noticed:

-- if I refresh the details page for a torrent, the number of peers displayed in the table is unpredictable, and all of the connected peers are not displayed
-- the peer table is almost always truncated in the middle of a row (see html excerpt 1)
-- occasionally an extra column is added and one row will start with a blank cell and have all of the other cells shifted over (see html excerpt 2)
-- looking at the page source, I have yet to see a </html> tag, or even the </table> tag that closes the peer table

This stuff probably isn't a big deal as it doesn't really effect the functionality all that much. I can't confirm that this occurs for anyone else.
For reference, the machine uses perl version 5.8.8.

--Chad

html excerpt 1:
<TR><TD bgcolor="#d0d0d0" align=center>Ci<TD bgcolor="#d0d0d0" align=center>Ci
<TD bgcolor="#ffe5e5" align=right> 90%
<TD align=right>-<TD align=right>-
<TD bgcolor="#e0bbff" align=right>D= 32&nbsp;K<TD bgcolor="#e0bbff" align=right>U= 1280&nbsp;K</TR>
<TR bgcolor="#ccffcc"><TD colspan=5>exbc0x01014C4F5244A41B8E330B25D2019769<TD colspan=2 align=center>62.106.22.185<TD>BitLord 1.1</TR>

[Charles Parker]

Logged In: YES
user_id=1816836
Originator: YES

Excerpts got cut off, sry. here they are:

html excerpt 1:
<TR><TD bgcolor="#d0d0d0" align=center>Ci<TD bgcolor="#d0d0d0" align=center>Ci
<TD bgcolor="#ffe5e5" align=right> 90%
<TD align=right>-<TD align=right>-
<TD bgcolor="#e0bbff" align=right>D= 32&nbsp;K<TD bgcolor="#e0bbff" align=right>U= 1280&nbsp;K</TR>
<TR bgcolor="#ccffcc"><TD colspan=5>exbc0x01014C4F5244A41B8E330B25D2019769<TD colspan=2 align=center>62.106.22.185<TD>BitLord 1.1</TR>
<TR><TD bgcolor="#d0d0d0" align=center>Ci<TD bgcolor="#d0d0d0"
--eof--

html excerpt 2:

<TR bgcolor="#ccffcc"><TD colspan=5>-AZ3110-a0QRiNOuJUny<TD colspan=2 align=center>81.84.150.116<TD>Azureus 3110</TR>
<TR><TD bgcolorffcc"><TD colspan=5>-BC0100-!'@e0xD6570654870BD370<TD colspan=2 align=center>218.124.66.13<TD>BitComet 0100</TR>

[dholmes999]

My apologies for letting this go so long without a response, but this is very likely due to the limited socket I/O handling in CTCS. It isn't nearly as robust as ctorrent itself, and cheats a bit by using nonblocking I/O without a proper buffering facility. The issue is likely more noticable with particular platforms, long peer lists, and/or latency between CTCS and the browser. I don't see it on my usual system for instance, though did recognize something similar when testing a prior version in another environment (and only partially fixed it, apparently). I'm working on addressing this with the next major client release.