Thanks Dianne, that sounds promising although I'm wary it will open up a nasty can of worms.
When you say "skip the whole content provider API" do you mean, access the underlying database directly (through helper methods of course) or not use the database at all? I'm not sure I'm going about this the right way. Essentially I pulled in the DownloadService class and then gradually pulled in more and more referenced classes until the thing compiled. I commented out Media-specific & SSL code because those are not relevant to what I'm doing. I ended up with about 30 classes which I placed in a single new package (I felt it was safer to isolate the code rather than use original package names). I also had to pull in a bunch of resources (strings, styles and a layout). I haven't done anything about the native method calls, which I'm sure I will find out about later. Now, I haven't tried running anything yet because I'm thinking I may be going down an increasingly rocky and treacherous path, so was hoping for some feedback before I get lost or twist my ankle! On 18 February 2011 14:21, Dianne Hackborn <hack...@android.com> wrote: > Just copy the networking code out of the platform source. It has been > there since 1.0. Personally I would skip the whole content provider API > that is built on top of that, since that is a lot of complexity for no > benefit for something that is all running inside the app. (Even for > something for access to another app, the content provider API is > questionable.) > > > On Thu, Feb 17, 2011 at 11:09 PM, Mark Carter <mjc1...@googlemail.com>wrote: > >> I would love to take advantage of the new DownloadManager introduced in >> Gingerbread, but since I'm aiming to keep my app cupcake-compatible, this is >> quite problematic. >> >> Are there any plans to make a library available for pre-Gingerbread >> support? If not, are there any known technical hurdles that would prevent a >> library from being created (relatively painlessly) based on the Gingerbread >> code? >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to android-developers@googlegroups.com >> To unsubscribe from this group, send email to >> android-developers+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en > > > > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > 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 android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en