Well there is a couple ways to do this. Well, probably more, but only 2 come to
mine right away. The first is to use a value object cfc. This is basically
a facade for the rest of your webservices. That is to say, lets say you have
like 20 different cfc's/webservices. Well, you make one cfc that has methods
that wrap up the functionality of the 20 worker cfc's. This way you make one
service connection and call methods that transparently call the cfc's that are
working behind the scenes. So no more managing connections and services, you
just have one service that supplies data from all the others. What I do is put
this in the master swf. So all of my webservice calls look like this
_level0.myService.myMethod(params); Well actually I have some _level0 function
that calls the webservice, but that's just because I like to have one master
swf to code in and the rest to design in. This way no matter what swf file I
load into any _level, i can just make that call to access the appropriate data.
This is also a fuseboxish way to handle security, because you can set public
type roles on the facade cfc and have that cfc invoke invoke child cfc's. The
child cfc's would be locked down to only allow access from the facade. Sean
Cornfield wrote a nice little article reguarding value object design patterns
here.
http://www.actionscript.com/index.php/fw/1/simplified-flash-remoting/
The only problem is that once you download the files and are filled with warm
fuzzies, you realize that there are 4 guys that you are going to have to get to
agree to let you use thier copywritten code. It would be great if they would
wrap all of that up into a commercial package so you could just buy it and use
it. However, reading the article and coarsing thru the classes will give you
some ideas on how you want to attempt something similar. Hope that helps.
Sean Renet
