One approach is to put the service configuration details in an XML file and load it during application start up using HTTPService.
I am thinking of something that is 100% client side. That is, the mock data services is just XML data files. I can load up a config file at application startup for parameters, but it won't help me link with the correct library. I would like to NOT have the mock data service code in my production application.
The only way I can think of not having ANY mock services in the production code is to take them out manually. Your program for mocking purposes is going to have to be able to know where these services/object are and how to contact them. I'm sure if it had to be done , you could use some mass of modules and event maps.
I was just made aware of conditional compliation in ActionScript...I think the answer to leaving the code out may be in there somewhere....