If you don't need the networking code, I don't think there is much benefit. The rest of the download manager is involved with lots of complexity for handling multiple clients and protecting them from each other (lots of that wrapped up in the content provider), the UI for looking at the downloads (which can't be provided as a .jar), etc.
On Mon, Feb 21, 2011 at 2:59 AM, Marcus Wolschon < [email protected]> wrote: > > > On 18 Feb., 18:48, Dianne Hackborn <[email protected]> wrote: > > I am just > > thinking to only use the networking pieces from it, and write your own > > front-end (posting notifications if that is what you want, or doing > whatever > > UI you want). > > Then what would be the benefit left? > Before the download manager you wrote your own UI and did the http-get/ > post/whatever-request > +error-handling already. > > -- > 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 > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
