blocks|key|3051855|text|Here+is+what+the+Android+SDK+says+about+sendStickyBroadcast()|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3051856|3051857|执行一个“粘滞”的意图(SendBroadcast)，这意味着您发送的意图在广播完成后仍然存在，这样其他人就可以通过registerReceiver(BroadcastReceiver，IntentFilter)的返回值快速检索该数据。在所有其他方面，这与sendBroadcast(Intent)的行为相同。|blockquote|3051858|3051859|3051860|通过操作系统发送的粘滞广播的一个示例是ACTION_BATTERY_CHANGED。当您为该操作调用registerReceiver()时--即使使用null+BroadcastReceiver+--您也会得到上次为该操作广播的Intent。因此，您可以使用它来查找电池的状态，而不必注册电池中所有未来的状态更改。|3051861|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/reference/android/content/Context.html#sendStickyBroadcast(android.content.Intent))^0|14|L|0|1P|0|0|0|0|0|0|J|M|1E|I|23|4|28|H|36|6|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|F|3|-4|5|6|7|11|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|12|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|13|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|14|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]]]

<a href="http://developer.android.com/reference/android/content/Context.html#sendStickyBroadcast(android.content.Intent)" rel="noreferrer">Here is what the Android SDK says about <code>sendStickyBroadcast()</code></a>:

<blockquote>
 Perform a sendBroadcast(Intent) that
 is "sticky," meaning the Intent you
 are sending stays around after the
 broadcast is complete, so that others
 can quickly retrieve that data through
 the return value of
 registerReceiver(BroadcastReceiver,
 IntentFilter). In all other ways, this
 behaves the same as
 sendBroadcast(Intent).
</blockquote>

One example of a sticky broadcast sent via the operating system is <code>ACTION_BATTERY_CHANGED</code>. When you call <code>registerReceiver()</code> for that action -- even with a <code>null</code> <code>BroadcastReceiver</code> -- you get the <code>Intent</code> that was last broadcast for that action. Hence, you can use this to find the state of the battery without necessarily registering for all future state changes in the battery.

blocks|key|3265601|text|类型+:-局部、正常、有序和粘滞|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3265602|正常广播|3265603|:-使用sendBroadcast()|3265604|:-异步广播|3265605|:-任何接收器接收广播，而不是任何特定的命令|3265606|有序广播|3265607|:-使用sendOrderedBroadcast()|3265608|:-同步广播|3265609|:-接收器以优先级为基础接收广播|3265610|:-我们也可以简单地中止这种类型的广播|3265611|本地广播|3265612|:-仅当广播仅在同一进程内使用时使用|3265613|粘滞广播|3265614|:-正常的广播意图在系统发送和处理后不再可用。|3265615|:-使用sendStickyBroadcast(Intent)|3265616|:-相应的意图是粘性的，这意味着您正在发送的意图在广播完成后仍然存在。|3265617|:-正因为如此，其他人可以通过registerReceiver(BroadcastReceiver，IntentFilter)的返回值快速检索该数据。|3265618|:-除了这个与sendBroadcast(Intent)相同。|3265619|entityMap^0|0|2|0|0|4|0|0|0|0|0|4|0|0|0|0|0|0|4|0|0|0|4|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1I|8|@$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1L|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1M|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1N|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1R|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1S|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1T|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|1U|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1V|8|@$9|1W|A|1X|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|1Z|8|@$9|20|A|21|B|C]]|D|@]|E|$]]|$1|13|3|14|5|6|7|22|8|@]|D|@]|E|$]]|$1|15|3|16|5|6|7|23|8|@]|D|@]|E|$]]|$1|17|3|18|5|6|7|24|8|@]|D|@]|E|$]]|$1|19|3|1A|5|6|7|25|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|6|7|26|8|@]|D|@]|E|$]]|$1|1D|3|-4|5|6|7|27|8|@]|D|@]|E|$]]]|1E|$]]

Types :- Local,Normal,Ordered and Sticky

Normal Broadcast

:- use sendBroadcast()

:- asynchronous broadcast

:- any receiver receives broadcast not any particular order

Ordered Broadcast

:- use sendOrderedBroadcast()

:- synchronous broadcast

:- receiver receives broadcast in priority base

:- we can also simply abort broadcast in this type

Local Broadcast

:- use only when broadcast is used only inside same process

Sticky Broadcast

:- normal broadcast intent is not available any more after this was send and processed by the system.

:- use sendStickyBroadcast(Intent)

:- the corresponding intent is sticky, meaning the intent you are sending stays around after the broadcast is complete.

:- because of this others can quickly retrieve that data through the return value of registerReceiver(BroadcastReceiver, IntentFilter).

:- apart from this same as sendBroadcast(Intent).

blocks|key|3265638|text|sendbroadcast()+-普通广播，但我们也可以设置优先级。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|3265639|sendstickybroadcast()+-与此一起传递的意图将为通过代码(动态接收器)注册的未来用户提供支持。将继续使用android的广播，并将重新传送或重新广播给来自任何广播接收器的未来请求|3265640|当有人使用sendstickyBroadcast(intent);发送粘性广播时，该广播将可供使用动态接收器的未来用户使用。|3265641|但是现在您不应该使用sendStickyBroadcast()方法，它已被弃用|3265642|来自Android文档：|3265643|3265644|此方法在API级别21中已弃用。不应使用粘滞广播。它们没有提供安全性(任何人都可以访问它们)，没有保护(任何人都可以修改它们)，以及许多其他问题。推荐的模式是使用非粘滞广播来报告发生了变化，并使用另一种机制让应用程序在需要时检索当前值|blockquote|3265645|3265646|3265647|我希望这能帮到你。|3265648|entityMap^0|0|F|0|F|0|0|L|0|L|0|5|S|0|A|L|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|D]]|E|@]|F|$]]|$1|I|3|J|5|6|7|18|8|@$9|19|A|1A|B|D]]|E|@]|F|$]]|$1|K|3|L|5|6|7|1B|8|@$9|1C|A|1D|B|D]]|E|@]|F|$]]|$1|M|3|N|5|6|7|1E|8|@]|E|@]|F|$]]|$1|O|3|-4|5|6|7|1F|8|@]|E|@]|F|$]]|$1|P|3|Q|5|R|7|1G|8|@]|E|@]|F|$]]|$1|S|3|-4|5|6|7|1H|8|@]|E|@]|F|$]]|$1|T|3|-4|5|6|7|1I|8|@]|E|@]|F|$]]|$1|U|3|V|5|6|7|1J|8|@]|E|@]|F|$]]|$1|W|3|-4|5|6|7|1K|8|@]|E|@]|F|$]]]|X|$]]

<code>sendbroadcast()</code> - normal broadcast, but we can set priority as well.

<code>sendstickybroadcast()</code> - intent passed with this will be stick for future users who are registering through code (dynamic receivers).
The broadcast that will stick with android, and will be re-delivered or re-broadcasted to the future requests from any broadcast receivers

When somebody sends a sticky broadcast using <code>sendstickyBroadcast(intent);</code> then that broadcast will be available for the future users who are using dynamic receivers.

But Now you should not use <code>sendStickyBroadcast()</code> method it is deprecated

From Android Documentation:

<blockquote>
 This method was deprecated in API level 21. Sticky broadcasts should
 not be used. They provide no security (anyone can access them), no
 protection (anyone can modify them), and many other problems. The
 recommended pattern is to use a non-sticky broadcast to report that
 something has changed, with another mechanism for apps to retrieve the
 current value whenever desired
</blockquote>

I hope this helps.

What is the difference between <code>sendStickyBroadcast</code> and <code>sendBroadcast</code> in Android?

what is the difference between sendStickyBroadcast and sendBroadcast in Android

Android

安卓系统中的sendStickyBroadcast和sendBroadcast有什么不同？

问安卓系统中的sendStickyBroadcast和sendBroadcast有什么不同
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安卓系统中的sendStickyBroadcast和sendBroadcast有什么不同EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问安卓系统中的sendStickyBroadcast和sendBroadcast有什么不同
EN