Yes, it makes most sense to wait for system B interface specs - then you can write System A interface. You may take a risk and modify system A's CFCs to call the System A interface since you know what data you need. System A interface may use simQuery to simulate connection to system B interface which you don't know about.
As more systems need to connect to system B that system may add new interface or expand current one and make it "global" - depends on a setup. As for your 2nd paragraph, if system A needs to connect to system C, D and I as well to get some data, you probably should develop another interface(s) in system A for all these connections - keep it tidy. TK -----Original Message----- From: Richard White [mailto:[EMAIL PROTECTED] Sent: Friday, September 22, 2006 11:24 AM To: CF-Talk Subject: Re: Designing for Integration thanks for your help tom. This makes alot of logical sense. So i suppose there is nothing i can do until i find out about the system B interfaces. Then if my system is system A, and it gets data from system b, c, and d, i will need to develop a different cfc (or set of cfc's) that will interface with each of the systems individual interface cfc's. Thanks again tom ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:253860 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
