hi,

i was wondering if anyone knows of a solid solution regarding =
controlling the amount of time a user can record netstreams if client =
records from client side. ive tested various methods and ive only come =
up with one method that seems to work, and that is to publish a live =
stream from the client to server and on server side do a ns.record and =
ns.play(name, -1, totTime). to that effect if totTime is reached an =
event is triggered and i close the stream and set writeAccess to "". =
however, i have found recording from server isnt as good as recording =
from client. my problem with recording from cleint is i havent found a =
way to securely end recording ability. if code is hacked and user =
decides to record indefinately, it would fill up disk space rather =
quickly. that idea just isnt sitting right with me.=20

when recording from client, i have tried setting writeAccess on server =
to "" in the middle of the recording but it doesnt seem to take effect =
till after the recording stops, so in that scenario, setting writeAccess =
does me no good. i would like to record from client securely if at all =
possible. any comments or suggestions are greatly appreciated.

thanks in advance,

adam

=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Adam,

Why not have a start and stop function for ns.record using the Date()
object for a timer?

HTH,
Bill
On Jun 13, 2005, at 7:31 AM, adam@jewdoo wrote:

> hi,
>
> i was wondering if anyone knows of a solid solution regarding
> controlling the amount of time a user can record netstreams if
> client records from client side. ive tested various methods and ive
> only come up with one method that seems to work, and that is to
> publish a live stream from the client to server and on server side
> do a ns.record and ns.play(name, -1, totTime). to that effect if
> totTime is reached an event is triggered and i close the stream and
> set writeAccess to "". however, i have found recording from server
> isnt as good as recording from client. my problem with recording
> from cleint is i havent found a way to securely end recording
> ability. if code is hacked and user decides to record indefinately,
> it would fill up disk space rather quickly. that idea just isnt
> sitting right with me.
>
> when recording from client, i have tried setting writeAccess on
> server to "" in the middle of the recording but it doesnt seem to
> take effect till after the recording stops, so in that scenario,
> setting writeAccess does me no good. i would like to record from
> client securely if at all possible. any comments or suggestions are
> greatly appreciated.
>
> thanks in advance,
>
> adam
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>



bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

I simply start an interval when rec is pressed, counting down by 1 every
second and when recordingtime >= allowedtime I stop the recording
programmatically

Stefan



-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.
org] On Behalf Of Bill Sanders
Sent: Monday, June 13, 2005 12:39 PM
To: FlashComm Mailing List
Subject: Re: [FlashComm] controlling amount of time user can record

Adam,

Why not have a start and stop function for ns.record using the Date() object
for a timer?

HTH,
Bill
On Jun 13, 2005, at 7:31 AM, adam@jewdoo wrote:

> hi,
>
> i was wondering if anyone knows of a solid solution regarding
> controlling the amount of time a user can record netstreams if client
> records from client side. ive tested various methods and ive only come
> up with one method that seems to work, and that is to publish a live
> stream from the client to server and on server side do a ns.record and
> ns.play(name, -1, totTime). to that effect if totTime is reached an
> event is triggered and i close the stream and set writeAccess to "".
> however, i have found recording from server isnt as good as recording
> from client. my problem with recording from cleint is i havent found a
> way to securely end recording ability. if code is hacked and user
> decides to record indefinately, it would fill up disk space rather
> quickly. that idea just isnt sitting right with me.
>
> when recording from client, i have tried setting writeAccess on server
> to "" in the middle of the recording but it doesnt seem to take effect
> till after the recording stops, so in that scenario, setting
> writeAccess does me no good. i would like to record from client
> securely if at all possible. any comments or suggestions are greatly
> appreciated.
>
> thanks in advance,
>
> adam
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>



bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Hi Bill, thanks for your reply.

im not altogther sure if you mean on the client side or server side but
being that there is no .record on client its my guess you mean on server.

the thing is, on the server, i have no problem ending a recording stream at
a given time. if im doing ns.play(name, -1, totTime), the play ends at
totTime, the event is triggered and then i call a function to close out the
stream and disable writeAccess to said client. i would rather not record
from the server. its so much cleaner to record from the client and it seems
the quality and playback are better if recording straight from client. when
i record from the cleint though, i am unable to securely regulate
writeAccess. in order to disable writeAccess to the client, the client has
to have ended the ns.publish(name, "record") before it will take effect.
know what i mean? 

thanks in advance,

adam

----- Original Message -----
From: "Bill Sanders" <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@pub
lic.gmane.org>
Sent: Monday, June 13, 2005 1:39 PM
Subject: Re: [FlashComm] controlling amount of time user can record


> Adam,
>
> Why not have a start and stop function for ns.record using the Date()
> object for a timer?
>
> HTH,
> Bill
> On Jun 13, 2005, at 7:31 AM, adam@jewdoo wrote:
> 
>
>
>
> bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>



=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Adam,

I was talking about the CS. As soon as you invoke ns.publish
("fileName", record), start the timer. and then fire ns.close() when
the time's up. Stefan's method is equally effective and simple. I
agree that recording on the CS is a lot cleaner.

HTH,
Bill
On Jun 13, 2005, at 7:52 AM, adam@jewdoo wrote:

> Hi Bill, thanks for your reply.
>
> im not altogther sure if you mean on the client side or server side
> but being that there is no .record on client its my guess you mean
> on server.
>
> the thing is, on the server, i have no problem ending a recording
> stream at a given time. if im doing ns.play(name, -1, totTime), the
> play ends at totTime, the event is triggered and then i call a
> function to close out the stream and disable writeAccess to said
> client. i would rather not record from the server. its so much
> cleaner to record from the client and it seems the quality and
> playback are better if recording straight from client. when i
> record from the cleint though, i am unable to securely regulate
> writeAccess. in order to disable writeAccess to the client, the
> client has to have ended the ns.publish(name, "record") before it
> will take effect. know what i mean? 
>
> thanks in advance,
>
> adam
>
> ----- Original Message ----- From: "Bill Sanders"
> <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
> To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@p
ublic.gmane.org>
> Sent: Monday, June 13, 2005 1:39 PM
> Subject: Re: [FlashComm] controlling amount of time user can record
>
>
> 
>
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Hi Stefan, than you for your reply.

i do the same thing on the client as a matter of fact. on the client, when
myTimer >= maxTime, i close out the ns.publish(name, "live") and then make a
call to server to close out its ns.play and ns.record and set the client
writeAccess to "".

on the server, ns.play(name, -1, totTime) is my failsafe. i set totTime to 5
seconds longer then what i set my timer to on the client, this way if some
unforseen something happens like code being tampered with, the ns on the
server ends and writeAcess is set to "".

its a bit tricky as there are multiple calls from server to client, and
client to server to prep, init, end and validate etc, but it works and
disables the ability to write to server from client when i want it to. but,
it a lot of steps that i would love to circumnavigate if i can. but i dont
see a certain way of disabling the ability to publish a "record" stream from
client that wont be effected by an annoymous who changes cleint side code.
not to mention recording from client seems to have better quality and
playback quality then publishing a live stream to server and recording it
from server.

maybe im being overly cautious, but i feel its better to be safe the have a
lot of potential downtime once i finally get my site online.

thanks in advance,

adam.

----- Original Message -----
From: "Stefan Richter" <stefan-fMeCE+ULXElEfu+5ix1nRw@public.gmane.org>
To: "'FlashComm Mailing List'" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@p
ublic.gmane.org>
Sent: Monday, June 13, 2005 1:46 PM
Subject: RE: [FlashComm] controlling amount of time user can record


>I simply start an interval when rec is pressed, counting down by 1 every
> second and when recordingtime >= allowedtime I stop the recording
> programmatically
>
> Stefan
>
>
>
> -----Original Message-----
> From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
> [mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gman
e.org] On Behalf Of Bill Sanders
> Sent: Monday, June 13, 2005 12:39 PM
> To: FlashComm Mailing List
> Subject: Re: [FlashComm] controlling amount of time user can record
>
> Adam,
>
> Why not have a start and stop function for ns.record using the Date()
> object
> for a timer?
>
> HTH,
> Bill
> On Jun 13, 2005, at 7:31 AM, adam@jewdoo wrote:
> 
>
>
>
> bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>



=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Hi Bill,

my concern is somebody changing code on client side. like removing that part
about ns.close. in doing that, disk space will fill rapidly not to mention a
lot of costly bandwidth used up.

this idea keeps me awake nights 

thanks in advance,

adam

----- Original Message -----
From: "Bill Sanders" <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@pub
lic.gmane.org>
Sent: Monday, June 13, 2005 2:07 PM
Subject: Re: [FlashComm] controlling amount of time user can record


> Adam,
>
> I was talking about the CS. As soon as you invoke ns.publish ("fileName",
> record), start the timer. and then fire ns.close() when  the time's up.
> Stefan's method is equally effective and simple. I  agree that recording
> on the CS is a lot cleaner.
>
> HTH,
> Bill
> On Jun 13, 2005, at 7:52 AM, adam@jewdoo wrote:
> 
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>



=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Adam,

Just a quick one. If you're concerned about changing code, you can
use a "SS Security" bounce -- before starting the record, a call to a
SS script looks for a variable related to key elements associated
with the timing. It's super easy to code, and it's difficult to hack.

HTH,
Bill

On Jun 13, 2005, at 8:12 AM, adam@jewdoo wrote:

> Hi Bill,
>
> my concern is somebody changing code on client side. like removing
> that part about ns.close. in doing that, disk space will fill
> rapidly not to mention a lot of costly bandwidth used up.
>
> this idea keeps me awake nights 
>
> thanks in advance,
>
> adam
>
> ----- Original Message ----- From: "Bill Sanders"
> <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
> To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@p
ublic.gmane.org>
> Sent: Monday, June 13, 2005 2:07 PM
> Subject: Re: [FlashComm] controlling amount of time user can record
>
>
> 
>
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>

bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

if you deploy a referrer check as well as edit your vhost.xml then noone can
take your swf, modify it and connect to your server. What they can do is
hotlink the swf but they cannot modify code and run it.

Stefan



-----Original Message-----
From: flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.org
[mailto:flashcomm-bounces-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@public.gmane.
org] On Behalf Of adam@jewdoo
Sent: Monday, June 13, 2005 1:12 PM
To: FlashComm Mailing List
Subject: Re: [FlashComm] controlling amount of time user can record

Hi Bill,

my concern is somebody changing code on client side. like removing that part
about ns.close. in doing that, disk space will fill rapidly not to mention a
lot of costly bandwidth used up.

this idea keeps me awake nights 

thanks in advance,

adam

----- Original Message -----
From: "Bill Sanders" <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@pub
lic.gmane.org>
Sent: Monday, June 13, 2005 2:07 PM
Subject: Re: [FlashComm] controlling amount of time user can record


> Adam,
>
> I was talking about the CS. As soon as you invoke ns.publish ("fileName",
> record), start the timer. and then fire ns.close() when  the time's up.
> Stefan's method is equally effective and simple. I  agree that recording
> on the CS is a lot cleaner.
>
> HTH,
> Bill
> On Jun 13, 2005, at 7:52 AM, adam@jewdoo wrote:
> 
[vbcol=seagreen] 
[vbcol=seagreen] 
[vbcol=seagreen] 
[vbcol=seagreen] 
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>



=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Hi Bill,

thanks for your reply, im looking into it.

adam
----- Original Message -----
From: "Bill Sanders" <wdsanders-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: "FlashComm Mailing List" <flashcomm-1Ss2GqJETD3yZ38Mhd3e/9ZfFG6BLHNm@pub
lic.gmane.org>
Sent: Monday, June 13, 2005 2:20 PM
Subject: Re: [FlashComm] controlling amount of time user can record


> Adam,
>
> Just a quick one. If you're concerned about changing code, you can
> use a "SS Security" bounce -- before starting the record, a call to a
> SS script looks for a variable related to key elements associated
> with the timing. It's super easy to code, and it's difficult to hack.
>
> HTH,
> Bill
>
> On Jun 13, 2005, at 8:12 AM, adam@jewdoo wrote:
> 
>
> bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]