invoke a CFC as needed, which could certainly work. However, then you would
still need some other application to respond to 3rd party "events" and put
them on the queue. At that point, if seems easier just to have a "gateway"
that invokes a CFC directly. If you need it asynchronous, then that CFC
could then put some message on the queue.
-Matt
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf Of Dick Applebaum
> Sent: Wednesday, August 18, 2004 1:52 PM
> To: CF-Talk
> Subject: Re: Event Gateway on BlueDragon, etc. ( was:BLACKSTONE: Software
> Development Times Article)
>
> I am new to JMS, so be gentle :)
>
> Wouldn't it be practical to use a cfmessage tag to set up a listener...
> something like:
>
> <cfmessage
> mode=SetListner
> MessageType=queue or topic
> MessageName= QueueName or TopicName
> Component=path to CFC
> Method=Function to invoke
> />
>
> Couldn't this be used to implement something like:
>
> http://www.devx.com/Java/Article/20903/0/page/3
>
> See the link to listing 1 (asynchronous reader) at the bottom of the
> page.
>
> Where:
>
> 1) the cfmessage tag sets up the listener and denotes a cfc. to be
> invoked when the listener fires
>
> 2) the CFC method receives the message in the argument named its input
> parameter & processes the message as desired.
>
>
> Certainly there are a lot more details, but this would be the overall
> approach
>
> Practical?
>
> Dick
>
> On Aug 18, 2004, at 10:11 AM, Matt Liotta wrote:
>
> > > 3) your thoughts on the tradeoffs of a cfmessage tag vs an event
> > gateway
> > >
> > One major tradeoff is the ability for CFML to be invoked based on a
> > message.
> > With a cfmessage tag you still need the CFM or CFC making use of it to
> > execute. An event gateway or something of similar design would invoke
> > CFML
> > based on some 3rd party input.
> >
> > -Matt
> >
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
