Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.

Posts: 1,474
Registered: ‎04-14-2009
My Device: Not Specified

Re: net.rim.device.api.io.Seekable in 5.0 -- the point?

Slightly tangential, but am I right to assume that reading/caching the resource/file into a byte[] stored in memory is not an option in your case?

Posts: 40
Registered: ‎03-29-2009
My Device: Storm 9550
My Carrier: AT&T

Re: net.rim.device.api.io.Seekable in 5.0 -- the point?

That's right.  The motivation behind wanting to use seek(), is to avoid having to keep a large file in memory at all times.  I want the OS to support seek(), and let them worry about developing the code to set the cursor position in a file without keeping all data in memory.  That logic has nothing to do with my application, and it's been an OS-level feature in all sorts of operating systems for decades, on computing platforms much less capable than a BlackBerry Storm.