help me understand some base points of FCS

i'm using a shared hosting and most of my clients will either. so modify the
current version of an audioComponent will not be allowed , but what if i
duplicate (just to dosen't have to reinvent the wheel) the audioComponent
and do the improvements i need and use it?

can i do that? and if i can where should i put the modified AudioComponent
asc file? i guess the main.asc will have to load it just like the MM built
in comps.


thanks for the help,


best,
rod.


"JayCharles" <webforumsuser@macromedia.com> escreveu na mensagem
news:egoe0d$76o$1@forums.macromedia.com...
> Correct... you will need access to your scriptlib files to modify them.
> Are you
> running your own FMS, or are you using shared hosting?
>
> Modifying the component asc files will affect other apps running on the
> same
> vHost. The solution to that one is to set up a separate vHost for your
> app,
> with it's own scriptlib directory (assuming you're running your own FMS...
> if
> you're not, you can't set up vHosts).
>

Correct... you will need access to your scriptlib files to modify them. Are you running your own FMS, or are you using shared hosting?

Modifying the component asc files will affect other apps running on the same vHost. The solution to that one is to set up a separate vHost for your app, with it's own scriptlib directory (assuming you're running your own FMS... if you're not, you can't set up vHosts).

hi jay, thanks for the explanation, helped a lot.

so the main.asc that has a load(components.asc) will load this file that
actually loads all the component's asc. and make them avaliable to use, i
guess it loads the files from the FCS Server that usually the user don't
have access to change.

what if i want to make some changes to those files (customize them), let's
say put a new method or change something in the simpleconnect.asc file?
i don't think i'll will be able to do because i don't have access to those
files right?

i'll look for the book you mentioned.

best,
rod.

"JayCharles" <webforumsuser@macromedia.com> escreveu na mensagem
news:egjbv1$r07$1@forums.macromedia.com...
> Yes... the directory name is the application name, so it must match the
> application name in your rtmp string exactly.
>
> The main.asc files (and all asc files for that matter) contain
> actionscript
> that will run on the server (those files are part of FMS, not part of
> Flash).
> They aren't compiled into the .swf
>
> When an application starts, it loads main.asc . In your case, main.asc is
> needed to load the component classes from the scriptlib.
>
> The scriptlib contains the asc files the server requires to interact with
> the
> client side communication components.
>
> I'd suggest picking up a copy of "Programming Flash Communication Server"
> (O'Reilly). It covers all of the basics, and it will give you an
> understanding
> of how client/server communication works.
>
>

Yes... the directory name is the application name, so it must match the application name in your rtmp string exactly.

The main.asc files (and all asc files for that matter) contain actionscript that will run on the server (those files are part of FMS, not part of Flash). They aren't compiled into the .swf

When an application starts, it loads main.asc . In your case, main.asc is needed to load the component classes from the scriptlib.

The scriptlib contains the asc files the server requires to interact with the client side communication components (as well as some other things you don't need just yet).

I'd suggest picking up a copy of "Programming Flash Communication Server" (O'Reilly). It covers all of the basics, and it will give you an understanding of how client/server communication works.