On 2005-03-24 16:12:38 +0100, Urs Janßen wrote: > afer compiling tin with -DDEBUG and calling it with "-D 1" it shows > that tin doesn't feeze but is damned slow (the XHDR XREF fallback > code doesn't look very optimal, but as it usualy shouldn't be needed > at all that's "ok").
What do you mean by slow? I did a top, and tin was taking 0% CPU time. Or was it doing transfers with the server? > if you don't like that feature you can recompile with > --disable-xhdr-xref. on 'normal' configured servers this is no > disadvantage, but on servers which do not have the Xref:full in > thier overviews tin isn't able to mark crossposted articles as read > when one of them is read. I don't understand. When doing a catchup, tin shouldn't mark the crossposted versions as read since they haven't been read. This is particularly important when an article is crossposted to a low-bandwidth group and a high-bandwidth group (or a group on a less important topic). In the latter one, I don't have the time to read everything, so that I often do a catchup there without checking in details first. Or there could be an option concerning the catchup behavior. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / SPACES project at LORIA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
