1 2 Previous Next 21 Replies Latest reply on Oct 21, 2009 7:05 PM by ataylor Go to original post
      • 15. Re: RESTful Queue implementation
        bill.burke

         

        "timfox" wrote:

        void acknowledge(String queueName, long messageID)- acknowledges all messages up to messageID in named queue


        That wouldn't work for what I need. I would need to acknowledge only one message at a time because there could be multiple "workers".

        I think we're going to need to deal with timeouts too.
        In a session-less approach, if a client removes a message from a queue and consumes it, then crashes or exits without acknowledging that message, then _at some point_ that message should be put back on the queue so it becomes re-available for consumption by other clients.


        Don't you have this problem of timeouts with any distributed session as it is used right now? or do you close() the session if the socket becomes disconnected?


        How would this timeout be configured? Would we would allow clients to specify a timeout, or should it be implementation specific server side config, hidden from the client?


        How do you deal with timeouts now? What would be cool is if JbossWeb could give callback noifications when keep-alive goes down.

        • 16. Re: RESTful Queue implementation
          ataylor

           

          Don't you have this problem of timeouts with any distributed session as it is used right now? or do you close() the session if the socket becomes disconnected?


          If the underlying connection is closed the session is closed on the server either via an interrupt signal or a timeout if say a network cable is unplugged

          How do you deal with timeouts now? What would be cool is if JbossWeb could give callback noifications when keep-alive goes down.


          What about http session timeouts, any way this could be used.

          also bear in mind that we have a netty http transport, I'm not sure if that could fit into th epicture somewhere, would we want the standalone hornetq server to support REST

          • 17. Re: RESTful Queue implementation
            bill.burke

             

            "ataylor" wrote:

            also bear in mind that we have a netty http transport, I'm not sure if that could fit into th epicture somewhere, would we want the standalone hornetq server to support REST


            I am using RESTEasy and RESTEasy has an abstraction to support other HTTP implementations. I originally had one for Grizzly, but pulled it out because I didn't want to support it.

            • 18. Re: RESTful Queue implementation
              timfox

               

              "ataylor" wrote:
              [would we want the standalone hornetq server to support REST


              Yes, absolutely - this is a core feature for 2.1, see roadmap:

              http://www.jboss.org/community/wiki/Roadmap



              • 19. Re: RESTful Queue implementation
                timfox

                 

                "bill.burke@jboss.com" wrote:

                That wouldn't work for what I need. I would need to acknowledge only one message at a time because there could be multiple "workers".


                That's fine - it would be just as easy to implement that

                I
                Don't you have this problem of timeouts with any distributed session as it is used right now? or do you close() the session if the socket becomes disconnected?


                Yes, if the client is lost then after a timeout sessions would be closed.

                However this is somewhat different - since there will be no specific connection with REST

                • 20. Re: RESTful Queue implementation
                  bill.burke

                  Thanks for all the input guys. Your input allowed me to generate a bunch of ideas and I think I have a solution that can use HornetQ AS-IS.

                  I'd like to schedule some time in the near future to present everything to you on a con-call.

                  • 21. Re: RESTful Queue implementation
                    ataylor

                     

                    "bill.burke@jboss.com" wrote:
                    Thanks for all the input guys. Your input allowed me to generate a bunch of ideas and I think I have a solution that can use HornetQ AS-IS.

                    I'd like to schedule some time in the near future to present everything to you on a con-call.



                    sounds good Bill, looking forward to it!

                    1 2 Previous Next