Again, to kind of echo what Brendan said, if this guy can't figure out simple remoting to a Coldfusion server, I would question my choice. Coldfusion is by far the simplest, most "plug and play" remoting to Flex there is, and there is plenty of documentation available showing you exactly how to do it. The one caveat with working with a remote server is that you need to make sure you configure your channelset if you are setting up your remoting in Actionscript as opposed to using the MXML tag.
On Mon, Jan 7, 2013 at 4:58 PM, Brendan Meutzner <bmeutz...@gmail.com>wrote: > ** > > > Do you have a code repository for the ColdFusion content setup? (ie. > Subversion, CVS, TeamSite, etc...) > > I have never debugged against a remote ColdFusion server, but it looks > possible: > > > http://help.adobe.com/en_US/ColdFusionBuilder/Using/WS0ef8c004658c1089-31c11ef1121cdfd6aa0-7fef.html > > You'll need to have RDS enabled on your remote server... instructions here > if you already have CF installed... I am not sure if you need to have > included it during the ColdFusion install, or if you can simply enable > after the fact. > > > http://helpx.adobe.com/coldfusion/kb/disabling-enabling-coldfusion-rds-production.html > > If you have a code repository, then you could check out your central CF > code to any development or production machine allowing you to keep that > common set of files you desire. Then you can have your development > versions of ColdFusion using this code, and allowing you to setup the debug > environment locally. To my knowledge, you're not going to be able to run > MS Access on the Mac environment, however, that's not a big deal... just > host the MS Access content on a remote server, and setup your local CF > development version to have a datasource pointing to the remote database. > > I use Mac for my development environment, and target Windows and Linux > production servers. Having the code repository allows me to develop > locally with my Mac environment, with local CF, database and Flex > content... when I'm ready, I simply synchronize with repository and then do > the same on my production versions to get the most up to date code. > Setting up the local Mac dev environment with CF and Flex is very straight > forward. You use the same services-config.xml, remoting-config.mxml files > as you have on the production server to define end points for RemoteObject > calls, so everything in seamless when the code hits the server. In your > Flex project properties, you target your local version of the > services-config.xml file (which sits in the > .../Coldfusion8/wwwroot/WEB-INF/flex-config directory locally) and when the > application compiles, it uses the defined configuration here. Once it is > on the server, you have the same version of the file running on your > ColdFusion instance and everything is fine. > > In short, take the time and make the effort to get a proper development > version running, and don't try to develop against remote servers. > Regardless of Windows or Mac, you want all of your developers to use > remote development environments. I've worked on teams with mixed OS > environments like this, and it's possible to do. > > If you're interested, and have the budget, I can spend a couple hours with > you to get the right environment setup. All of the Flex development I've > done since 2004 is against ColdFusion backends and I'm more than familiar > with it. If you think we can solve this with general questions via this > forum, then I'm happy to help here as well... but there's only so much you > can solve with generalizations vs. actually seeing your setup and being > able to help hands on. > > I hope this helps a bit, and feel free to continue to ask questions... > > > Brendan > > > On Mon, Jan 7, 2013 at 3:49 PM, Mark Fuqua <m...@availdata.com> wrote: > >> be > > > >
