I believe Corfield has an article that describes this (although, again I believe, they use a "facade CFC", a whole CFC, that gives remote access to an internal CFC).
http://www.macromedia.com/devnet/mx/flashremoting/articles/facades.html
The idea is that you decide what your public web services (or Flash Remoting) interface should be and code a web-accessible CFC containing those methods with access="remote" and then have each of those methods provide the necessary security / authentication before calling the non-web-accessible methods. You can follow Camden's suggestion (getFoo() and remoteGetFoo() in the same CFC) or use two separate CFCs. The benefit of using separate CFCs is that you can design the remote interface for the convenience of your users but design the 'internal' CFC as better model of your internal system.
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
