flash data integration: Is there a support document somewhere that explains the different types of data
integration (xml, cfc etc...) and which method is most effective? Is there one
method that's better or more efficient than the rest? I realize it can depend
on different circumstances but I'm just looking for a general rule of thumb.

Thanks!!

I'd say there really is no general rule of thumb. The application's
requirements and the deployment enviroment will play a large role in
determining the ideal source for the data, and the developer's level of skill
will be a factor in how efficiently or effectively that data source can be
used. Another issue that will work as a factor in deciding on technologies is
cost. I suppose when planning a project, the developer should ask his/her self
"do I need the client to buy a proprietary software package, or can I get the
job done with open source offerings?".

I personally like things that are open source and portable, so (when it comes
to web delivery) I tend to use XML, PHP, mySQL, and AMFPHP to handle my data
whenver possible. Sometimes those technologies aren't enough to get the job
done, but I've found form most of my applications they are sufficient. Going
this route not only keeps the cost down, but it makes life very easy when the
IT people decide to move from Windows to *nix and vice-versa.

Like JayCharles I would rank availability of resource expertise high on the
list. If it is just you yourself and you, you have your answer. If you have
a inhouse staff to do the work, then them. If you have budget to hire from
outside, then you have more choices.

Portability can be near the top but some client really do not care as they
are a vendor specific shop and that is that. Open source (technologies with
a long track record only) versus vendor specific technology does not sway me
much as long as they have a track record of support. In general an active
developer community is critical these days so you can find answers to stuff
you will not find in vendor support open source or not. However I will go
with JayCharles and for my own projects look for low cost proven reliable
deployment and that is usually open source.

The trump on everything is the client (unless they request you to make the
choices for them). For example I would prefer XML but a client had select
URL vars. So that is what you did. A client selected ASP years after ASP.Net
was out and that is what we did. A client selected JavaScript for ASP server
scripts and that is what we did (and my preference in this case).



--
Lon Hosford
www.lonhosford.com
May many happy bits flow your way!
[quoted text, click to view]
I'd say there really is no general rule of thumb. The application's
requirements and the deployment enviroment will play a large role in
determining the ideal source for the data, and the developer's level of
skill
will be a factor in how efficiently or effectively that data source can be
used. Another issue that will work as a factor in deciding on technologies
is
cost. I suppose when planning a project, the developer should ask his/her
self
"do I need the client to buy a proprietary software package, or can I get
the
job done with open source offerings?".

I personally like things that are open source and portable, so (when it
comes
to web delivery) I tend to use XML, PHP, mySQL, and AMFPHP to handle my
data
whenver possible. Sometimes those technologies aren't enough to get the job
done, but I've found form most of my applications they are sufficient. Going
this route not only keeps the cost down, but it makes life very easy when
the
IT people decide to move from Windows to *nix and vice-versa.