I see the ids used by the Uri matcher are private, and so is the matcher its self.
I think it would be an improvement to make them protected and to provide a protected access method for the mather, sumthing like:
protected int getUriId(Uri uri) {
return mUriMatcher.match(uri);
}
This would be useful for the following use cases:
I have an override for openFile with need to ensure that the Uri is actually for an image, (currently using get type and checking the string witch is slower than checking an int).
i would like to override trySetNotificationUri and if I am given an action uri such as content://provider/table/type/# I want to set the notification uri to content://provider/table in order to get the right notifications. (currently to do this I think I might need to create a new matcher to identify these uris)
I see the ids used by the Uri matcher are private, and so is the matcher its self. I think it would be an improvement to make them protected and to provide a protected access method for the mather, sumthing like:
This would be useful for the following use cases:
openFilewith need to ensure that the Uri is actually for an image, (currently using get type and checking the string witch is slower than checking an int).trySetNotificationUriand if I am given an action uri such ascontent://provider/table/type/#I want to set the notification uri tocontent://provider/tablein order to get the right notifications. (currently to do this I think I might need to create a new matcher to identify these uris)Thank you