Re: [Slashcode-development] comment question

[CertIndex.com W. <web...@ce...>]

----- Original Message -----
From: "Ask Slashdot Guy" <cl...@sl...>
To: <sla...@li...>
Sent: Tuesday, 17 April, 2001 22:07
Subject: Re: [Slashcode-development] comment question


>
> 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.

Oh, no!

>
> *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.

Aha, and what is the difference between indexed mode and 'non-indexed mode'? I looked into this a
while ago I believe and I think it only applies to nested displaytype correct? If so then it's not
relevant to us since we only have 'flat' and 'threaded', and comments never 'break out' of their
thread status and show fully. Only when they are on the 'comment level' that is being viewed are
they shown.

>
> 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.

Ahh, why / 2 ? Why not just 'ignore' comments after the 'overload mode' threshold is met? So if you
have a story with 1000 comments and you set the 'overload mode' threshold to 500, the user only has
500 of the most recent comments to work with. (well i guess unless they display oldest first, in
which case they'd only have 500 of the oldest comments to work with)

>
> Sites with bandwidth concerns will definitely want to look into this value.
>
> Sorry abuot the confusion. Hope this clears everything up.
>

ah no problem, Slash is somewhat a beast and taming it isn't an easy thing. ;-)

> - Cliff
>
> _______________________________________________
> Slashcode-development mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-development
>