在活动之间共享数据 使用实例登录后传递邮件

“email”是可以用来引用正在请求的活动的值的名称

1登录界面代码

Intent openLoginActivity = new Intent(getBaseContext(), Home.class);
    openLoginActivity.putExtra("email", getEmail);

主页上的2个代码

Bundle extras = getIntent().getExtras();
    accountEmail = extras.getString("email");

如果你的意图是从当前Activity调用其他Activity，你应该使用intent。您可以将重点放在按需共享数据而不是持久化数据上。

However, if you really need to persist these values then you could persist them in some kind of structured text file or database on local storage. A properties file, XML file, or JSON file could store your data and be easily parsed during activity creation. Don't forget also that you have SQLite on all Android devices, so you could store them in a database table. You could also use a Map to store key-value pairs and serialize the map to local storage, but this might be too cumbersome to be useful for simple data structures.

假设你使用Intent从活动一调用活动二。 你可以通过intent.putExtra()传递数据，

拿着这个作为你的参考。 使用Intent.putExtra发送数组

希望这是你想要的。

如果你想处理数据对象，这两个实现非常重要

Serializable和Parcelable

Serializable is a marker interface, which implies the user cannot marshal the data according to their requirements. So when object implements Serializable Java will automatically serialize it. Parcelable is android own serialization protocol. In Parcelable, developers write custom code for marshaling and unmarshaling. So it creates less garbage objects in comparison to Serialization The performance of Parcelable is very high when comparing to Serializable because of its custom implementation It is highly recommended to use Parcelable implantation when serializing objects in android.

公共类User实现了Parcelable

点击这里查看更多信息

Using the hashmap of weak reference approach, described above, and in http://developer.android.com/guide/faq/framework.html seems problematic to me. How are entire entries reclaimed, not just the map value? What scope do you allocate it in? As the framework is in control of the Activity lifecycle, having one of the participating Activities own it risks runtime errors when the owner is destroyed in advance of its clients. If the Application owns it, some Activity must explicitly remove the entry to avoid the hashmap from holding on to entries with a valid key and a potentially garbaged collected weak reference. Furthermore, what should a client do when the value returned for a key is null?

在我看来，由应用程序拥有或在单例中拥有WeakHashMap是更好的选择。映射中的值是通过键对象访问的，当不存在对键的强引用时(即所有活动都使用键及其映射到的对象完成)，GC可以回收映射条目。

我有一些想法，但我不知道它们是否是你想要的。

您可以使用一个保存所有数据的服务，然后将活动绑定到该服务以进行数据检索。

或者将您的数据打包为可序列化或可打包的，并将它们附加到一个bundle中，并在活动之间传递该bundle。

这可能根本不是你要找的，但你也可以尝试使用SharedPreferences或一般的首选项。

不管怎样，让我知道你的决定。