Adobe 38043740 - ColdFusion Standard - Mac Development Manual page 1261

DEVELOPING COLDFUSION 9 APPLICATIONS
Using External Resources
• A directory lookup robot IM "buddy" that responds to messages chat contain an employee name with the
employee's phone number or buddy ID.
Server to serve examples
• A JMS subsystem that publishes status updates that business intelligence systems consume.
• A system that monitors and publishes download events from a website.
Event gateway terms and concepts
This document uses the following terms when referring to event gateways:
A trigger that ColdFusion can receive from an external source. ColdFusion event gateways receive events.
Event
The information provided by an event. In ColdFusion, a message is the data structure that the event gateway
Message
receives when an event is triggered.
Java code that receives events and sends them to and from ColdFusion application code. This
Event gateway
document uses the term event gateway, without the word type or instance, for the general concept of a ColdFusion
event gateway. Where the context makes the meaning obvious, the term can also mean event gateway type or event
gateway instance.
A specific event gateway implementation, represented by a Java class. Each event gateway type
Event gateway type
handles messages belonging to a particular a communications method or protocol, such as short message service
(SMS), an instant messaging protocol, or Sockets. You generally have one event gateway type per communication
protocol. You configure each event gateway type on the Gateway Types page in the Event Gateways area in the
ColdFusion Administrator.
A specific instance of an event gateway type class. You configure each event gateway instance
Event gateway instance
on the ColdFusion Gateway Instances page by specifying the event gateway type, an ID, the path to the event gateway
application CFC that uses this instance, and a configuration file (if needed for the selected event gateway type). You
can have multiple event gateway instances per event gateway type, for example, for different event gateway
applications.
One or more CFCs and any supporting CFM pages that handle events from an event
Event gateway application
gateway instance and send messages using the event gateway instance. The event gateway application is not part of an
event gateway instance, but the code that is responsible for processing event messages to and from the instance.
Code in an event gateway that receives events from an event source and passes them to the
Event gateway listener
ColdFusion gateway service for delivery to a CFML listener CFC.
A CFC that contains one or more methods that respond to incoming messages from one or more event
Listener CFC
gateway instances. Part of an event gateway application.
ColdFusion gateway service
path between an event gateway instance and listener CFCs.
The part of ColdFusion that provides underlying support for event gateways, including a
Last updated 1/20/2012
1256