In a generalist sense adapter pattern is a bridge between 2 classes that have some common functionality, but the interfaces are not reusable between them. Ideally the need for adapter arises when we have two classes that are not developed keeping in mind interaction between them.
Strategy pattern, is more of a future reuse pattern, and that is the intent its in android framework, reuse and extensibility. Just thinking here, I could be wrong. Siddharth On Feb 13, 12:50 pm, TreKing <[email protected]> wrote: > On Fri, Feb 12, 2010 at 11:32 PM, MCON Dev <[email protected]> wrote: > > Should it be ArrayStrategy instead ? > > Why? > > ------------------------------------------------------------------------------------------------- > TreKing - Chicago transit tracking app for Android-powered > deviceshttp://sites.google.com/site/rezmobileapps/treking -- 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
