Today, I had been thinking of a feature that can be very valuable to be added to the RADBook framework. And that is what I call "Page Streaming". I suggest to add a feature to the book, as when a user goes to a page, the book would automatically load the following X pages ready to be viewed. The X can be designated by the developer. For example when the end user goes to page 20, at first page 20 and 21 are loaded and displayed and after they are displayed, the RADBook would automatically load page 22 and 23 while the user is looking at page 20 and 21. This way two pages are always cached ahead of time (minimum). This way the start loading is fast and the experience is very smooth. I had mentioned it before under the word "Virtualization" but I like "Page Streaming better" :-)
What do you think Kiril? :-)
..Ben
[update]
I forgot to mention two (three) very important benefits with this system and that is the "Bandwidth" cost for publishing large number of books to large number of audiences and server load. Let's say I have a book that is 500 pages with lots of images and 1000 users view the book in one day. Not to mention time!
a) If the book attempts (at client side) to create 500 pages for each viewer, there will be a large amount of data generated by server (server load) and transferred to client (bandwidth load) before the client can see. Not to mention the time consumed to create and transfer. And imagine the viewer would only look at the first few pages. Lots of wasted time and resources.
b) That same book can look so much faster and thinner if "Page Streaming" was incorporated.
These are the things which will make RADBook a major contender!
Hope these are valuable feedback!
What do you think Kiril? :-)
..Ben
[update]
I forgot to mention two (three) very important benefits with this system and that is the "Bandwidth" cost for publishing large number of books to large number of audiences and server load. Let's say I have a book that is 500 pages with lots of images and 1000 users view the book in one day. Not to mention time!
a) If the book attempts (at client side) to create 500 pages for each viewer, there will be a large amount of data generated by server (server load) and transferred to client (bandwidth load) before the client can see. Not to mention the time consumed to create and transfer. And imagine the viewer would only look at the first few pages. Lots of wasted time and resources.
b) That same book can look so much faster and thinner if "Page Streaming" was incorporated.
These are the things which will make RADBook a major contender!
Hope these are valuable feedback!
2 Answers, 1 is accepted
0
Accepted
Valentin
Top achievements
Rank 1
Rank 1
answered on 20 Dec 2009, 08:11 PM
Hi Ben,
this is something we definitely want to add in the Q1 timeframe. We were thinking for a similar mechanism. We will need to cache and the previous pages also, not only the next.
More details to come soon.
Best regards,
Valentin Stoychev
The Telerik team.
this is something we definitely want to add in the Q1 timeframe. We were thinking for a similar mechanism. We will need to cache and the previous pages also, not only the next.
More details to come soon.
Best regards,
Valentin Stoychev
The Telerik team.
0
Ben Hayat
Top achievements
Rank 2
Rank 2
answered on 20 Dec 2009, 08:32 PM
Excellent my friend and thanks for reply on Sunday!
I actually thought about previous pages as well, but I didn't want to sound too demanding :-)
"Leave it to Telerik team, for great engineering" My new signature!
..Ben
I actually thought about previous pages as well, but I didn't want to sound too demanding :-)
"Leave it to Telerik team, for great engineering" My new signature!
..Ben