Quote:
Originally Posted by DHR
Of course we have a standard. In fact lots of them. As long as you don't need to support DRM, HTTP is the obvious transmission protocol. In fact, even if you do have DRM, HTTP is fine.
|
Okay, here's the system I'm envisaging...
1) Consumer clicks on [Buy now] on the book they want at author/writer's page
2) Book appears on consumer's ereader and is ready to read
Every additional step in between is one more annoyance/potential-hiccup. Amazon has this fairly well optimised, for 3G or WiFi but is of course naturally restricted to the Amazon-Kindle world only.
The "interface/standard" I'm referring to is the method of loading the purchased book into the reader directly without end-user intervention, not the transport medium/protocol it uses to move the data there (eg, HTTP/SCP/FTP/email/RFC1149
My guess is that the Kindle polls Amazon periodically (30~60 seconds) with what ever unique ID/code it has, and then if there's a book pending for delivery it downloads it and adds it to the internal store. What I'm wishing for is that it could be possible to do this for all devices for all content providers - but it'll never happen, more for reasons of market protection (perceived by places like Amazon) than anything truly technical (ignoring 3G delivery given that Amazon did the hard-yards with that).