To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.admin.generalOpen lugnet.admin.general in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Administrative / General / 5982
5981  |  5983
Subject: 
Re: POST vs. GET (was: Re: IGNORE: yet another test message)
Newsgroups: 
lugnet.admin.general
Date: 
Thu, 6 Apr 2000 04:48:45 GMT
Reply-To: 
MATTDM@MATTDM.ORGspamless
Highlighted: 
(details)
Viewed: 
803 times
  
Todd Lehman <lehman@javanet.com> wrote:
  lugnet.foo.bar 40 60 70 70 80
  lugnet.bar.baz 70
  lugnet.glorp.gnort 80 80 90 90 90 90 90 90 100 100 100

Uh oh; now I'm confused again. I thought articles were rated, not groups.

Assuming that the above represent articles ("lugnet.foo.bar" = one post in
lugnet.foo?), then the rating shown on the web page would be:

lugnet.foo.bar 64
lugnet.bar.baz 70
lugnet.glorp.gnort 91

(assuming that the "current value" is just the average of all votes)?

I assume you don't want to calculate this on the server side to save CPU?
(It seems like doing so would vastly simplify the client side; instead of
needing to know about history and time and all that, it could just say:
gimmie a list of what everything is now. Or as a compromise: gimmie a list
of everything updated since I last checked.)

Maybe I'm missing something (like I said, I'm confused) but it seems like
it'd make sense to calculate the (new) current value whenever a new rating
is submitted, and store that. (I assume that articles will be read at least
an order of magnitude more often than they are rated.)


--
Matthew Miller                      --->                  mattdm@mattdm.org
Quotes 'R' Us                       --->             http://quotes-r-us.org/



Message has 2 Replies:
  Re: POST vs. GET (was: Re: IGNORE: yet another test message)
 
(...) No, that's correct. Articles are, groups aren't. But a client could, if it wanted to, start messages off with any default number (not necessarily 50) based on which group(s) the article appears in. (...) The server does store the new composite (...) (25 years ago, 6-Apr-00, to lugnet.admin.general)  
  Re: POST vs. GET (was: Re: IGNORE: yet another test message)
 
(...) I think that's a typo... should be "lugnet.foo.bar:666 40 60 70 70 80" :) (...) well the way I see it (and Todd might prove me wrong) is that this way the client has the freedom to do whatever it wants with the ratings... such as have a (...) (25 years ago, 6-Apr-00, to lugnet.admin.general)  

Message is in Reply To:
  Re: POST vs. GET (was: Re: IGNORE: yet another test message)
 
(...) Yeah -- what Dan said. I don't mean to send the entire _history_ with all the timestamps, but rather to send the raw data up to that point -- all the raw values -- (which is almost like the whole history) -- so that the client can calculate a (...) (25 years ago, 6-Apr-00, to lugnet.admin.general)

29 Messages in This Thread:








Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR