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 / 5975 (+10)
  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)
 
  Re: POST vs. GET (was: Re: IGNORE: yet another test message)
 
(...) That number doesn't actually exist anywhere until display time. That is, the initial 50 is never stored anywhere, and won't be reported to clients. It'll be up to clients to add in the 50 or whatever value they choose for whatever group(s) the (...) (27 years ago, 6-Apr-00, to lugnet.admin.general)  
 
  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)  

Next Page:  5 more | 10 more | 20 more
Redisplay Messages:  All | Compact

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