> But from what I have been able to learn about Blackstone it appears
> that one way to call CFCs asynchronously is with JMS.
JMS is not really a remote procedure call vehicle so it is not a "way
to call CFCs asynchronously".
> That is what Sean Corfield is doing, according to his blog & posts here.
Well, I am using Blackstone's event gateway to consume JMS messages
(asynchronously). In the same way that I'm using Blackstone's event
gateway to provide an IRC bot that joins a chat channel, listens to
messages and responds to them.
> JMS can run on a separate server/box and takes responsibility for
> routing and delivery of messages between clients (whether the clients
> are available or not).
Yup. We use JMS to transmit a lot of data around our organization. The
web front end uses JMS to transmit information about trial downloads,
product registrations, membership profile updates and so to the
relevant back end systems. We're doing more and more with JMS over
time but so far we've been limited to Java / C# for message consumers
(we already wrapped a Java message publisher in a CFC). With
Blackstone, we can use a simple Java consumer to pass messages to
ColdFusion for processing. This allows us to leverage existing CF code
that processes the same data that arrives through other protocols
(such as files on disk, via scheduled jobs).
> The "orders" are simple messages that go
> to the JMS provider -- they will sit there until an app is available to
> process them.
Yup. It helps decouple of the front end and back end systems (and data
is transmitted as standard XML, e.g., using OAGIS schemas).
--
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
