What I like to do is handle all the backend transactions first and make sure they work. So in your CFC you would have the functions that talk to the database to see if the user's supplied credentials are valid. It could return a boolean or what ever else you need, maybe a list of roles for the user. Make a cfml test page to test those functions. Typically my test pages use CreateObject to instantiate the same CFC that the Flex RemoteObject function will invoke. That way you can isolate any backend issues without any frontend complexity. Once you've got your backend CFC working, then hook in the Flex screen with the RemoteObject.
On Mon, Nov 24, 2008 at 9:55 AM, stinasius <[EMAIL PROTECTED]> wrote: > ok i dont mind using cfcs bt i think all am asking for is a clear > explanation on how to go abt it. any way thats possible? > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Alternative FAQ location: > https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847 > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > > -- Howard Fore, [EMAIL PROTECTED] "The universe tends toward maximum irony. Don't push it." - Jeff Atwood
