blocks|key|3022578|text|嗯，它们实际上是不同的。你似乎认为这几乎是一样的。在代码中注册接收器时，必须在应用程序被销毁时注销它(实际上，当注册它的Activity或Service被销毁时)。另一方面，当您在清单中声明它时，即使您的应用程序没有运行，也可以使其可用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3022579|问问你自己:这两种方法中哪一种最适合你的需求？|3022580|entityMap^0|1O|8|1X|7|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Well, they are actually different. You seem to think that it is almost same. When you register a receiver in code, you must unregister it when the app gets destroy (actually, when the <code>Activity</code> or <code>Service</code> that register it, gets destroy). On the other hand, when you declare it in the manifest, you make it available even if you app is not running.

Just ask your self: which of the two approaches best fits your needs?

blocks|key|3022666|text|我不能说一个比另一个的实现效率高(我的直觉告诉我，它太接近了，不太重要)，但出于Cristian的回答中暗示的原因，以编程方式注册和注销可能会使您的应用程序更有效率。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3022667|如果您在清单中注册，则任何与您的筛选器匹配的意图都会唤醒您的广播接收器。如果您以编程方式注册，则只能允许在特定时间唤醒接收器，并且您可以控制哪些意图将唤醒接收器以及在哪些时间唤醒接收器。|3022668|如果你真的担心在不需要的时候唤醒接收器，那么在代码中以编程的方式来做。您需要更加小心地始终取消注册，并确保您的接收器始终按照您期望的那样注册，但如果您正确地这样做，您可以避免不必要地唤醒您的接收器，从而节省一些效率。|3022669|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I can't speak as to the efficiency of the implementation of one over the other (my intuition tells me that it's too close to really matter), but for reasons hinted at in Cristian's answer, registering and unregistering programmatically might make your app more efficient.

If you register in the manifest, your broadcast receiver will always be woken up by any intents that match your filters. If you register programmatically, you can only allow your receiver to be woken up at particular times, and you can control which intents will wake up your receiver and at which times.

If you're really worried about waking up the receiver at times that it doesn't need to be, then do it programmatically in the code. You'll need to be more careful to always unregister, and ensure that your receiver is registered at all times that you expect it to be, but if you do that correctly, you can avoid waking up your receiver unnecessarily, and thus saving some efficiency.

blocks|key|4638111|text|这取决于场景。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4638112|何时使用哪种方法注册|offset|length|style|BOLD|4638113|使用哪种方法注册您的BroadcastReceiver取决于您的应用程序对系统事件做了什么。我认为你的应用程序想要了解系统范围内的事件主要有两个原因：|4638114|4638115|您的应用程序围绕这些事件提供某种类型的服务|ordered-list-item|4638116|您的应用程序希望对状态更改做出优雅的反应|4638117|4638118|第一类的例子是需要在设备启动时立即工作的应用程序，或者在安装应用程序时必须启动某种工作的应用程序。Battery+Pro或App2SD就是这类应用的很好的例子。对于此类型，必须在清单文件中注册BroadcastReceiver。|4638119|第二类的例子是发出信号改变你的应用程序可能依赖的环境的事件。假设您的应用程序依赖于已建立的蓝牙连接。你必须对状态变化做出反应--但只有当你的应用程序处于活动状态时才能做出反应。在这种情况下，不需要静态注册的广播接收机。动态注册会更合理。|4638120|还有一些事件，您甚至不允许静态注册。这方面的一个例子是每分钟广播一次的Intent.ACTION_TIME_TICK事件。这是一个明智的决定，因为静态接收器将不必要地耗尽电池。|4638121|entityMap^0|0|0|A|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|14|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|15|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

It depends on scenario.

When to use which method to register

Which method to use for registering your BroadcastReceiver depends on what your app does with the system event. I think there are basically two reasons why your app wants to know about system-wide events:

<ol>
<li>Your app offers some kind of service around these events</li>
<li>Your app wants to react graciously to state changes</li>
</ol>

Examples for the first category are apps that need to work as soon as the device is booted or that must start some kind of work whenever an app is installed. Battery Widget Pro or App2SD are good examples for these kinds of apps. For this type you must register the BroadcastReceiver in the Manifest file.

Examples for the second category are events that signal a change to circumstances your app might rely on. Say your app depends on an established Bluetooth connection. You have to react to a state change – but only when your app is active. In this case there is no need for a statically registered broadcast receiver. A dynamically registered one would be more reasonable.

There are also a few events that you are not even allowed to statically register for. An example for this is the Intent.ACTION_TIME_TICK event which is broadcast every minute. Which is a wise decision because a static receiver would unnecessarily drain the battery.

blocks|key|744072|text|简单地说|type|unstyled|depth|inlineStyleRanges|entityRanges|data|744073|动态注册-您的应用程序期望在应用程序运行时立即发生一些事情|744074|静态注册--从长远来看，你的应用程序正在等待一些事情发生。因为你不能保证你的应用程序在它发生的时候会运行，所以你可以礼貌地要求android系统在它运行时通知你|744075|在这一点之后，它们将具有相同的执行。|744076|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Simply put

Dynamic Registration - Your app expects something to happen immediately while the app is running

Static Registration - You app is waiting for something to happen over the long term. And since you cannot guarantee your app will be running when it happens you can politely ask the android system to notify you when it does

They both would have the same execution beyond that point

I'm writing a simple broadcast receiver. I've registered receivers in both the manifest and in the code before. For my purposes this is a simple receiver that doesn't need to do anything fancy.

Is there a reason to choose one method over the other in this case? Is registering the receiver in the manifest more efficient (executes faster)? Or are they both basically the same? 

I'm asking because the application I'm writing needs to be very efficient, and I haven't been able to find good information on the practical difference between the two methods. I'm trying to follow whatever is the best coding practice. 

Cheers

Is it better code practice to register a receiver in manifest or in code?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在写一个简单的广播接收器。我已经在清单和代码中注册了接收器。就我的目的而言，这是一个简单的接收器，不需要做任何花哨的事情。在这种情况下，是否有理由选择一种方法而不是另一种方法？在清单中注册接收者是否更有效率(执行速度更快)？或者它们基本上都是一样的？我之所以问这个问题，是因为我正在编写的应用程序需要非常高效，而我还...

问在清单中注册接收者还是在代码中注册接收者更好的代码实践？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在清单中注册接收者还是在代码中注册接收者更好的代码实践？EN