5 Replies Latest reply on May 18, 2011 10:51 AM by Andrig Miller

    AMQP Support - closed as WONTFIX

    talawahdotnet Newbie

      Hi,

       

      I noticed that HORNETQ-126 (Implement AMQP) was recently closed as WONTFIX.  Can somebody shed some light on the rationale behind that decision?

        • 1. AMQP Support - closed as WONTFIX
          Andrig Miller Novice

          At this point, the correct version of the specification to implement is the 1.0 specification, which is still in flux at this point.  It vastly simplified from the 0.10 spec.  Also, right now its just not a priority for us, as we really don't have a lot of demand for it at the moment.

           

          Of course, things could change in the future, and when the 1.0 specification stabilizes and their are other implementations out there, things may get revisited.

          • 2. AMQP Support - closed as WONTFIX
            talawahdotnet Newbie

            Ok. WONTFIX, seemed like a definitive rejection of AMQP, which is weird given RedHat's investment in AMQP and its usage in the upcoming cloud products.  Seems like moving it to a milestone called something like FUTURE would have been more in line with your explaination.

            • 3. AMQP Support - closed as WONTFIX
              Andrig Miller Novice

              talawahdotnet wrote:

               

              Ok. WONTFIX, seemed like a definitive rejection of AMQP, which is weird given RedHat's investment in AMQP and its usage in the upcoming cloud products.  Seems like moving it to a milestone called something like FUTURE would have been more in line with your explaination.

               

              It just didn't make sense to have a JIRA hang around for an unspecified period of time.

              • 4. AMQP Support - closed as WONTFIX
                borges Novice

                Andrig Miller wrote:

                 

                talawahdotnet wrote:

                 

                Ok. WONTFIX, seemed like a definitive rejection of AMQP, which is weird given RedHat's investment in AMQP and its usage in the upcoming cloud products.  Seems like moving it to a milestone called something like FUTURE would have been more in line with your explaination.

                 

                It just didn't make sense to have a JIRA hang around for an unspecified period of time.

                 

                Why not? Having cases like this assigned to FUTURE, or "Waiting For" would keep everyone interested well informed about it, and serve as well placed reminders of things we might want to do in future.

                 

                I mean, we do have a 'sort of unscheduled commitment to implementing AMQP if and when the spec comes out'. Why not use the issue tracker to, well, track this issue?

                • 5. AMQP Support - closed as WONTFIX
                  Andrig Miller Novice

                  Francisco Borges wrote:

                   

                  Andrig Miller wrote:

                   

                  talawahdotnet wrote:

                   

                  Ok. WONTFIX, seemed like a definitive rejection of AMQP, which is weird given RedHat's investment in AMQP and its usage in the upcoming cloud products.  Seems like moving it to a milestone called something like FUTURE would have been more in line with your explaination.

                   

                  It just didn't make sense to have a JIRA hang around for an unspecified period of time.

                   

                  Why not? Having cases like this assigned to FUTURE, or "Waiting For" would keep everyone interested well informed about it, and serve as well placed reminders of things we might want to do in future.

                   

                  I mean, we do have a 'sort of unscheduled commitment to implementing AMQP if and when the spec comes out'. Why not use the issue tracker to, well, track this issue?

                  Well, its pretty simple.  We may or we may not do it.  So, there's no point in communicating to the community that we will do it in the future, when we are unsure whether we ever will.  If customers start asking for it in HornetQ, and not just in MRG-M then product management will let us know, and we can open a new issue based on where it would fit in the schedule.