coldbox.system.remote.ColdboxProxy. This will give you the ability to locate and talk to your running ColdBox application so you can proxy in requests from remote systems like Flex/Air, Event Gateways, ColdFusion REST/Soap Web Services and even CFC data binding.
"A proxy, in its most general form, is a class functioning as an interface to something else. The proxy could interface to anything: a network connection, a large object in memory, a file, or some other resource that is expensive or impossible to duplicate" Wikipedia
process()method. This method expects an
eventargument to be passed to it which is the event string that will be executed for you and all the other arguments passed to this method will be converted and merged into the request collection according to their passed name.
Hint The advanced ColdBox templates gives you a sample proxy object in your
remotefolder in your application where you can store all your remote proxy objects.
Application.cfcmethods fire. By default, when using HTTP calls, ColdBox can auto-locate your application with no issues at all, but with Flex/AIR or other protocols you must set this location in your
COLDBOX_APP_MAPPINGdirective ONLY if not in the webroot of an application.
/and you won't modify this. But if your application is in a sub-folder then add the full instantation path here. So if your application is under
/apps/myAppthen the value would be:
COLDBOX_APP_MAPPINGvalue is an instantiation path value