| Naicu Octavian 2005-08-24, 5:53 pm |
| Well, take in consideration that in a worst-case
scenario every piece of client side code might be
rewritten into a new swf that connects to your server
and be used in malefic purposes!
Keeping as much of the code server ise is a safer way
to go, but keep the recording code client side and
ensure a big buffer, or else you will get verry badly
recorded videos because you can not use buffers!
The way I do recording is client side with a big
buffer. First the user presses 'record' .When the user
presses 'stop record' I do: myStream.attachVideo(null)
and go to a "Saving Movie..." state until what
remained is safely sent to the server.
--- Beto A <astro_sk-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:
>=20
> In a 1:N app with the controller being able to
> switch from a jpg/Video/SnapShot and audio(on/off)
> would you think it is better to keep the code on the
> clientside or the ServerSide??, take into
> consideration that recording will be thrown into the
> mix.
>=20
> What problems could arise from doing this
> clientside?....................Serverside?
>=20
> =20
>=20
> cheers
>=20
> =09
> ---------------------------------
> Start your day with Yahoo! - make it your home page
>=20
>=20
>
=3D-----------------------------------------------------------
> Supported by Fig Leaf Software -
> http://www.figleaf.com
>
=3D-----------------------------------------------------------
>=20
> To change your subscription options or search the
> archive:
>
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>=20
=09
________________________________________
____________
Start your day with Yahoo! - make it your home page=20
http://www.yahoo.com/r/hs=20
=20
=3D-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=3D-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
|