Re: [Slashcode-development] comment question

[Ask S. G. <cl...@sl...>]

On Tue, 17 Apr 2001 13:29:53 -0700, CertIndex.com Webmaster said:

> thanks a lot for taking the time to address this.
>  
>  let me give a scenario just to make sure i 'got it'.
>  
>  you have 1000 comments in a story.
>  
>  user sets his commentspill to 500 and his commentlimit to 100
>  
>  since commentspill is at 500, only 500 comments are 'acknowledged'. from that 500, they are divided
>  into pages, 100 comments each. so the user ends up with 5 pages of 100 questions each of 500 of the
>  1000 comments.
>  
>  correct?
>  
>  (if so, is it the 500 newest or oldest? or is that determined by how they sort the story.)
>  
>  thanks again
>  

ACK! I completely misinterpreted your question. This is what I get for trying
to answer technical details before my morning caffeine intake.

*COMMENTSPILL* is the threshhold a user sets so that they can get more
"threads" displayed per page on a story with a large number of comments. Put
simply, if a story goes over <commentspill> comments, then it is automatically
switched to indexed mode.

Some people prefer this than having to scroll thru 10-20 pages of comments to
see most of the threads.

Scenario:

A story is posted that is more popular than normal and it goes over 600
comments.

User A, with a commentspill set to 500 and preferred post mode of "nested" will
view the article and comments will be displayed in "indexed" mode, instead.

What I was referring to before was 'Overload Mode'. Slashdot has a "breaking"
variable, which when set, will effectively limit the maxiumum size of a users
CommentLimit setting. Basically if CommentLimit > Breaking, then CommentLimit =
Breaking / 2. 

Sites with bandwidth concerns will definitely want to look into this value.

Sorry abuot the confusion. Hope this clears everything up.

- Cliff