Right, something like a session is a bit easier to deal with. Put some data in the users session and it's available in any servlet they access until the session expires or the data is removed. If you want to think about things in terms of a session, it might be best to consider using a sqllite database.
I'm thinking more about the request scope though. I visualize an Intent as quite similar to sending a request to a servlet with optional data and then getting the page (Activity) back. I know it's not entirely comparable though. On Mar 24, 2:00 pm, Raja Nagendra Kumar <[EMAIL PROTECTED]> wrote: > Hi Dan, > > I see andorid application in the context of intents not like web > server and browser kind of app. If I understand your inputs correctly, > I would have wished intent data access should be as simple as who the > servlets share the data of http session with me not worrying about > serialization, parcelable.. > > > I don't see what you dislike about this > > Basically due to lack of authentic expertise in andorid :) and its > api.. similar to my early days of web programing.. > > Regards, > Nagendra > > On Mar 25, 12:43 am, "Dan U." <[EMAIL PROTECTED]> wrote: > > > > Why google not go with user creating a view object and > > > showing it (like in j2me). > > > As a disclaimer, I should say I have no experience with j2me. It might > > be easier to think of the Activity as a view. Think about it as a > > container view for your UI that happens to do a lot of other stuff. > > > > However if I could tell my application to run only in one vm, > > > can't avoid one activity for each screen. > > > I don't know why you say this. It would be possible to change the > > content view so you have one activity and multiple screens. I don't > > see how it has anything to do with running in multiple VMs. Although > > > > I am not feeling very > > > comfortable with data passing between the activity creations.. > > > I don't see what you dislike about this. It seems an awful lot like > > web programming to me, where you get/post requests to the server. I > > guess being that I'm mainly a web developer, I see that and it seems > > natural to me. > > > On Mar 24, 11:17 am, Raja Nagendra Kumar <[EMAIL PROTECTED]> > > wrote: > > > > Hi, > > > > Looking for any good documents and support from expects to understand > > > google desing on intents and why each screen should be created using > > > activities. Why google not go with user creating a view object and > > > showing it (like in j2me). > > > > One thing I understand that each activity could run in different vm's > > > etc.. However if I could tell my application to run only in one vm, > > > can't avoid one activity for each screen. I am not feeling very > > > comfortable with data passing between the activity creations.. > > > > I tried one activity to other activity data though static variables > > > instead of passing them through intent extra.. etc.. this seem to > > > work.. however not sure when this could fail.. > > > > Regards, > > > Raja Nagendra Kumar, > > > C.T.Owww.tejasoft.com-Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
