>> > * Why have Palm departed from broadcasting launch codes for
>> > notifications?
>>
>> Because sending a launch code to every app installed takes a lot of time,
>> if there are a lot of apps. With the notification manager, only the apps
>> who care get notified. Much, much faster.
>
>What's a long time, and what's much faster? Very subjective comments. I
>use launch
>codes all the time and do not experience problematic delays.
Launch codes aren't necessarily bad. What's bad is when a code is
broadcasted to every app on the device, when the odds are high that very
few of them care at all. If you've a ton of applications on your device
(as is more possible given the higher amounts of storage now available)
then it can be significant. Order 1 instead of O(N) if you want to get
pedantic :-)
Try installing a hundred applications on a device and change the time.
Compare that to changing the time on a blank device. There's a huge
difference. Launching an app isn't a simple process!
When you register for a Notification, you can have it send you a launch
code as your notification, no problem. It just doesn't send it to everyone
in the world too. That's the difference.
The old launch codes still get broadcast just like they used to. Can't
break that system. But things like power-on and power-off are sent via the
new Notification Manager, and thus only to apps who wanted to know, and
thus it doesn't slow down the user experience perceptibly.
>> Just use the creator id registry for the notification codes.
>
>Why not provide another one?
Time, effort, and that there's nothing to gain by doing so as far as I can
tell. It just has to be unique, that's all. If anyone wants to share
(publicize) a given code, there's nothing standing in your way, and
everyone has to play by your syntax and params for it because it is yours.
Perhaps I've missed something that makes a difference, but we don't need to
take on extra work without a very good reason...
-David Fedor
Palm Developer Support
