 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) Yup, that's what I mean. It'll be up to the client to calculate the ratings from the set of raw inputs for each article. --Todd (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) 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 (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message)
|
|
(...) No, I wouldn't be that cruel! :) :) (...) Absolutely, it can, yes. :) Any integer in the range 0 to 100 inclusive. The histogram display on the website snaps values to the nearest 10-stop. (...) Cool! --Todd (27 years ago, 6-Apr-00, to lugnet.admin.general)
|
| |
 | | 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 (...) (27 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 (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)
|