Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of wjamesjong@gmail.com designates
 209.85.214.176 as permitted sender)
From: James Jong <wjamesjong@gmail.com>
Content-Type: multipart/signed;
 boundary="Apple-Mail=_4E020051-1DF1-4CFB-BA7C-80B6EF947117";
 protocol="application/pgp-signature"; micalg=pgp-sha512
Message-Id: <B4E156B8-A2E0-461E-8853-650EB0EA812B@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [plugins] Proper handling of subsequant calls in Media plugin
Date: Fri, 2 Aug 2013 12:15:30 -0400
References: 
 <CAJOjTCih3XvuxsuvKZFdf-6=cWiPKNJrS+x58Rq4iYkcZCGY_A@mail.gmail.com>
 <CAASJe7_jCKBcDoQPAfJUAn+=wATPrTPa1=YAvYpeJ3Q2XXjNfw@mail.gmail.com>
To: dev@cordova.apache.org
In-Reply-To: 
 <CAASJe7_jCKBcDoQPAfJUAn+=wATPrTPa1=YAvYpeJ3Q2XXjNfw@mail.gmail.com>

--Apple-Mail=_4E020051-1DF1-4CFB-BA7C-80B6EF947117
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

For iOS, a play during play state would restart the audio at the =
beginning.  I agree we should have a consistent behavior that is =
documented.

-James Jong

On Aug 2, 2013, at 11:33 AM, Lorin Beer <lorin.beer.dev@gmail.com> =
wrote:

> I ran into this sometime ago on the android media API. The relevant
> conversation is likely deeply buried, and we should consider =
documenting
> the appropriate behavior somewhere permanent.
>=20
> My opinion is that appropriate behavior is dependent on the function =
being
> called and the current state. A FSM could capture this.
> In terms of <play> during <play> state, I would recommend that the =
plugin
> executes the latest command normally, playing media from a new source =
or
> restarting the currently executing media as if the play command had =
been
> received in the <stopped> state.
>=20
> - Lorin
>=20
>=20
> On Thu, Aug 1, 2013 at 1:47 PM, Benn Mapes <benn.mapes@gmail.com> =
wrote:
>=20
>> Working on https://issues.apache.org/jira/browse/CB-3783, it appears =
that
>> there is no documentation on how the media plugin should handle =
subsequent
>> calls of the same function.
>>=20
>> An example would be calling my_media.play() multiple times when the
>> my_media is already playing. Should this be swallowed by the plugin =
and
>> ignored? Should we respond with a
>> MediaError<
>> =
http://cordova.apache.org/docs/en/3.0.0/cordova_media_media.md.html#MediaE=
rror
>>> .MEDIA_ERR_ABORTED
>> and a message saying the media is already playing? What about =
subsequent
>> calls to my_media.pause() when the media is already paused?
>>=20
>> Was just wondering what other platforms have implemented for this and =
what
>> the proper way of handling subsequent calls is.
>>=20
>> ~Benn
>>=20


--Apple-Mail=_4E020051-1DF1-4CFB-BA7C-80B6EF947117
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJR+9tDAAoJEDGEz2BOh5dbR9QH/RoSdHWmNZOgLmRdeikGtaRj
5E19pHBYq/BdjOjCBOn6uDlGtQSGsoKAHyEIEQ2Kbr7+WiHPAgjE5fSws5TihnOO
FitWSD7wpQJlg6Bf07Iq9fHGNTuK6Rvi/Kk6dMIdjJfWtHlY5NA0r2ZkV8yE+n9d
Tmagf8EnrqVmrmGAxMG22K5E9v//PrKTBZYcS+xHs8imvYm8itP+DNymg31OEyTq
XvdiwhTKJjqF2zE1ebNrltiyx8FRjH+rlcLfMLh+V5eh8qzjXMNVDNiF2NAvs1bB
uuDYQKUSD2yMynQiHv+I97SjCMjIxuI70pIZPh27G63jsdEEV1z0VwW/SH4SPqY=
=ZFAq
-----END PGP SIGNATURE-----

--Apple-Mail=_4E020051-1DF1-4CFB-BA7C-80B6EF947117--