Details

    • New Feature
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • Backlog
    • Server
    • None

    Description

      We were discussing possible scenarios, especially regarding federated scenarios where multiple ESME servers wish to exchange messages. Lift already has RabbitMQ integration (http://scala-tools.org/mvnsites/liftweb/lift-amqp/scaladocs/index.html ) As an aside, I've got to say that I'm always surprised at what Lift already can do. This functionality would probably work well with our planned pool functionality. The idea would be that there are some pools that are federated across several servers. Until we have the pool functionality working, I like to suggest creating an action that sends a message via AMQP to another ESME server. Of course, we'd have to implement a AMQPAddListener to receive the messages sent via the action. This way we can learn more about messaging via AMQP. My suggestion would be that we create a second Stax instance that can act as a receiver to test out these enterprise messaging scenarios.

      Attachments

        1.
        AMQP Action Sub-task Open Unassigned
        2.
        AMQP listener Sub-task Open Unassigned

        Activity

          People

            Unassigned Unassigned
            rhirsch Richard Hirsch
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: