he architecture in my mind is that an rails application for account
management(credentials,credits,etc) and rest api and using
activemessaging for message distribution. there will be as many as
queues for each distrubtion type (eg sms queue, email queue). when a
request comes, the controller will send the message to the appropriate
queue. A processor will get the message from the queue, parses it and
runs the logic to deliver it.
Not Dennis Byrne: June 2007
in list: Rails ActiveMessaging Intro
more fromwww.inblogs.net
2Expand
Message Monster - activemessaging-discuss | Google Groups
in list: Rails ActiveMessaging Intro
more fromgroups.google.com
new process groups functionality - activemessaging-discuss | Google Groups
in list: Rails ActiveMessaging Intro
more fromgroups.google.com
Not Dennis Byrne: activemq rails ruby java ajax rest a13g activemessaging apache
in list: Rails ActiveMessaging Intro
more fromwww.inblogs.net
Beech Bonanza: June 2007
in list: Rails ActiveMessaging Intro
more fromwww.inblogs.net
flexonrails.net » Blog Archive » Publish\Subscribe Messaging with Flex and Rails using Apache ActiveMQ, ActiveMessaging, and STOMP
in list: Rails ActiveMessaging Intro
more fromflexonrails.net
Configuration - activemessaging - Google Code
in list: Rails ActiveMessaging Intro
more fromcode.google.com
ActiveMessaging - activemessaging - Google Code
in list: Rails ActiveMessaging Intro
more fromcode.google.com
InfoQ: Introduction to ActiveMessaging for Rails
in list: Rails ActiveMessaging Intro
more fromwww.infoq.com
Notation: * = Private bookmark and comment|… = Clipping [?] | … = Public highlight [?]
