Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming > #2067

Re: update checking

Show all headers | View raw

On 8/11/12 6:57 PM, bob wrote:
> Why does it often take software forever and a day to check if an update is available?  An example of this is Mac OS.  Isn't this just a matter of comparing the latest version of a component with the current version?
>
Well, what if you have 10 components? 100? 1000?

Also, what if you have privacy concerns.  I don't want Apple, Microsoft, 
or Google to know every component (or even type of component) that I 
have installed, so the updater can't just say "Here are the 100 things I 
have installed, what is the latest version?".

So, potentially a lot of data is being passed over the line, and 
bandwidth becomes a concern.

There are other techniques that can reduce bandwidth, but they increase 
CPU/Memory requirements for the server.

Some engineer found the best trade-off that lets the requests be served, 
and reduces the overall cost for his company.

Back to comp.programming | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

update checking bob <bob@coolfone.comze.com> - 2012-08-11 18:57 -0700
  Re: update checking Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-08-14 11:22 -0700
    Re: update checking Nomen Nescio <nobody@dizum.com> - 2012-08-15 11:35 +0200
      Re: update checking Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2012-08-16 08:38 -0700

csiph-web