Bug 11530 - InputStreamInvoker should allow read head to be moved forward
Summary: InputStreamInvoker should allow read head to be moved forward
Status: RESOLVED FEATURE
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.6.x
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-04-02 18:35 UTC by MPH
Modified: 2016-09-14 07:15 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FEATURE

Description MPH 2013-04-02 18:35:43 UTC
Assets.Open() returns an InputStreamInvoker, for which the following kinds of behaviors will throw an exception:

isi.Position += 100;
isi.Seek(100, SeekOrigin.Current);

While the underlying Java.io.InputStream does not support random access, it does allow moving the read head forward via the skip() function.

I propose that the implementation be adjusted to allow the position to be moved in one direction, in some fashion.
Comment 1 Atsushi Eno 2016-09-14 07:15:18 UTC
That sounded like a good idea, but it turned out to be impossible to implement that because it is impossible to get current Position which is necessary to implement Seek() to calculate return value. Thanks for the suggestion.