 | | Re: POST vs. GET (was: Re: IGNORE: yet another test message) —Dan Boger
|
| | | (...) 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)
|
| | | |
| | | | | Re: POST vs. GET (was: Re: IGNORE: yet another test message) —Matthew Miller
|
| | | | | (...) The downside, as I see it :) is that if the client just gets back one number per article somehow, it's an afternoon/evening hack to add this to a newsreader (like slrn) which already has GroupLens support. If the client has to actually process (...) (25 years ago, 6-Apr-00, to lugnet.admin.general)
|
| | | | | |
| | | | | | | Re: POST vs. GET (was: Re: IGNORE: yet another test message) —Todd Lehman
|
| | | | | | (...) Well, maybe we can do both. Depends on the bandwidth and frequency of calls. --Todd (25 years ago, 6-Apr-00, to lugnet.admin.general)
|
| | | | | | |
| | | | | | | | Re: POST vs. GET (was: Re: IGNORE: yet another test message) —Matthew Miller
|
| | | | | | (...) Well, I think it'd happen whenever slrn grabs headers for a newsgroup. That too much? (That would be in the case where there were a cgi which would take a list of articles [1] and return all values somehow. If it were a one request, one result (...) (24 years ago, 7-Apr-00, to lugnet.admin.general)
|
| | | | | | |
| | | | | Re: POST vs. GET (was: Re: IGNORE: yet another test message) —Todd Lehman
|
| | | | (...) Oh! YES! Thank you. That exactly. (...) Yop! --Todd (25 years ago, 6-Apr-00, to lugnet.admin.general)
|
| | | | |
