Yes, it's apparently public and I think I understand your concern, because it can break legacy code, but what you can do is to introduce yet another collection - "certificates", while leaving the old one in place and marking it as deprecated in the future versions. It's a traditional Java way of making changes.
On Jan 17, 10:28 am, Brian Carlstrom <[email protected]> wrote: > If this is part of the public API, then no, it probably not going to be > able to change. > > -bri > > > > > > > > On Tue, Jan 17, 2012 at 10:11 AM, Oleg Gryb <[email protected]> wrote: > > > > confusing. Could you call that 'ceritificates' instead and return > > > Certificate[] array instead of Signature[] array? > > > Can somebody please answer this qs as well? Probably I'm missing > > something here. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Android Security Discussions" 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-security-discuss?hl=en. -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" 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-security-discuss?hl=en.
