While I am sure any forward looking statement will need to be taken
with a grain of salt, perhaps you could alleviate many of our concerns
with some clue as to the timeframe in which we might expect relief on
this front. If we knew that in a month or two we could look forward
to at least
I can only tell you that the feature is done. The timing of when you
see a device in the field that supports it is up to the deployment
manager.
It's important to remember that Android is a platform, and just
because the platform advances doesn't necessarily mean that all
devices are advancing
On Dec 2, 5:22 am, Dorn Hetzel [EMAIL PROTECTED] wrote:
Maybe we need to start another mailing list for unrequited android
realtimeaudio:)
I'm all for focused discussion on this topic as it crosses between
native concerns and public APIs via the SDK. In my longer original
post I mentioned that
The reason this isn't in 1.0 is because we didn't want to ship a half-
baked API. We have a solution coming soon in the form of a flexible
base layer that supports push and pull models. For example, we have
built an InputStream object on top of it that we will offer as sample
code.
In the
Melody,
Unfortunately, this does seem to be the situation until at least the
next release of the SDK.
I am trying to find a way around it through other interfaces in the
native code, but I get the impression that even if I find one,
it won't actually be useable in combination with SDK code.
5 matches
Mail list logo
