Quote:
Originally Posted by petercreasey
B, interesting, no one had mentioned that kobo.com might have a server that won't allow more frequent updates. That is a reasonable explanation of why.
It does seem, though, that kobo should want their own site (kobo.com) to be the most up-to-date source.
|
I don't think you're understanding how this works yet. Kobo.com does not have a server that these updates are served from separate from the affiliates that are getting the update. Kobo the company has one server somewhere. And all Kobo devices no matter where they were bought from or where they are presently located or what their affiliate is labelled in their config file all call in to that server. If the device provides an affiliate name to the server that is flagged to get the update it gets it. If not, it happily does the rest of the sync stuff (small bandwidth vs pushing an update) but even though the update is sitting on the server the device is talking to it doesn't get it.
Why are devices with "Kobo" or "Kobo.com" as the affiliate not early in the rollout? Maybe there are a lot more devices out there with Kobo as the affiliate so that would overwhelm them. Maybe they'd rather some other affiliate take the flack if something goes wrong. All we KNOW is that they roll it out slowly by affiliate and the WHY (and why they use the order they do) is purely speculation. And FYI, it is NOT just the Kobo.com affiliate that gets a slow roll out.
NOTE TO ABOVE: yes, I realize that I oversimplified the server operation description somewhat to make my point (I assume it would be physically more than one server).