Re: how to unregister interuptListener registered in AudioSessionInitialize() on iPhone
Re: how to unregister interuptListener registered in AudioSessionInitialize() on iPhone
- Subject: Re: how to unregister interuptListener registered in AudioSessionInitialize() on iPhone
- From: Marc Vaillant <email@hidden>
- Date: Tue, 24 Feb 2009 16:01:40 -0500
- Mail-followup-to: William Stewart <email@hidden>, Christopher Atlan <email@hidden>, CoreAudio API <email@hidden>
On Mon, Feb 23, 2009 at 07:42:12PM -0800, William Stewart wrote:
> um - do NOT do this. In fact as you have published this, we'll probably
> break it
>
> This has not been used outside of that context and we make no guarantees
> that this will work - or continue to work - the way you currently "think
> it will"
>
> You need to use APIs and not to hack into the system and use private
> ones. You have no idea of the constraints under which those properties
> are used, or the limitations that they operate under.
Especially since Apple already does a fine job of yanking the rug from
under you with their mercurial public APIs:)
>
> The worst of it is, is that you guys hack around things like this, then
> we find that you've done this - usually badly - but your Apps stop
> working. Then we have to mop up the mess and try to figure out what you
> are doing, why you are doing it, and how we keep your ill-informed code
> working. Even worse, half the time when we're dealing with this, we are
> under tight deadlines, and you don't answer our calls (often because you
> feel guilty I guess of having done this in the first place)...
Apple brought that responsibility upon themselves with their app store
model, which isn't exactly taking them to the poor house. Not to
mention the choice of objective-c for most of the API, which makes it
extremely easy to pull private API signatures out of dylibs. If this is
a significant problem, it seems that Apple needs a way to more easily
and automatically detect API violations.
>
> If there is functionality that you want, then the right way to do this
> is to either bring the issue up with us on a mailing list, or
> preferably, write a bugreport describing the problem you are having, and
> what you would like to see changed to fix that.
Did you make it to the end of his blog post? He *did* do that.
Marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden