I think with all the comments we have a good start to what it *should* be. I agree with you bob, that we don't want the API to work based on what the device is, but rather an "abstraction of fixes" so to speak.
However, using the device identity could still work ok for this... we've been throwing around a locale-like method of finding the dataset for a specific problem. Although i understand the desire to test for a capability, I think that you can get enough detail on a specific implementation (including os build and carrier) that you can make the whole thing much lighter than if you were to run a bunch of test code. That not to say that you never want to... IMO we want to use whatever the best method is of determining a capability. Anyway, I certainly think there is room for discussion, and I think it should be assumed that prior to first release, we'll refactor the code over and over again :) - Brill Pappin -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
