 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) I guess the client doesn't really care about the history of the message rating, but that would be the best way to adjust the clients view of messages rating... though I assume the client will be able to query the ratings of a message (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) All I really want is a number representing the current cumulative-to-this-point score -- like what's displayed on the web page. (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) I think you'll be able to get that from the message headers, when you look it up... but most cases the message when you read it first will have a rating of 50 - assuming you get it as soon as it's posted, no one would have had a chance to rate (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: bug in partsref?
|
|
(...) well, just checked it with NN6pr1 for linux as well, and got the same result... the &150; isn't showing... I did look a bit today, but couldn't find an endash entity... anyone happen to know if the &####; is an official part of html? I wonder (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) Hmmm -- is that a planned feature? Current messages don't seem to have an X-Rating (hmmm, that sounds kinda funny) unless I am missing something. (Always possible!) Anyway, that would be plenty good for me. 1) I don't tend to keep my (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) As far as I know (haven't checked in the past 5 hours) it's not there yet - but Todd mentioned adding it to the avid.cgi at some point. (...) nod, that'll work for you. For what I'm planning to do, the spooling process will run all the time, (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) Me too. (What did you think I was thinking about?) (...) Yeh. For streaming clients, so they can update their ratings in an extremely time and bandwidth-efficient way. --Todd (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) A set of data resulting in that number. (...) Yah, the picture is becoming clear. I don't (yet) want anything so sophisticated.... (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | 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 (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
Todd Lehman wrote: [snip long good explanation] (...) nod, exactly what I meant. I was afraid you meant something like: lugnet.foo.bad:5321 80 lugnet.foo.bad:5321 40 lugnet.foo.bad:5321 70 lugnet.foo.bad:5321 50 lugnet.foo.bad:5321 -80 (a rating of (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)
|