There is no limitation -- you may run out of memory, though. That said, I wouldn't really recommend doing this for a situation where a user could just continue navigating indefinitely and wouldn't necessarily think about going back over everything they have visited. For example, the standard browser does all page navigation within a single activity.
On Thu, Aug 20, 2009 at 3:47 PM, mgpc <[email protected]> wrote: > > Is it necessary to limit how deep the activity stack can become within > an application? > > I'm implementing a browser-type app. Every time the user clicks a > link, I could launch a new PageView activity, but then the activity > stack might become very deep. Alternatively I could have a single > PageView activity that changes its content when a link is clicked, > maintains an internal history and overrides the BACK button. > > Is there anything performance-wise to choose between these two > designs? Is it OK to let the activity stack become arbitrarily deep? > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
