> I'd try to avoid copying and deleting the file each time, at least if it's > the same file.
In the stress test it's the same file, but in the real world it will be a new jar file every time, corresponding to updates to the plugin. > It's interesting to think about how the activity lifecycle and things like > orientation changes mean your process often gets terminated and then > recreated, in a way that's supposed to be invisible to the user. I wonder > if there's a reliable way to cause that to happen? It might be worth > looking into. That's an interesting idea. In practice I would bet that the process will pretty much always get terminated at some point before loading enough new plugins to cause a problem, but it would be pretty nice to be able to control that. Thanks, Matt -- 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
