Yes, currently we already have a way to track the actual message content. (with a small twist, unlike MSMQ, we are keeping messages around after they were sent or processed, this make debugging much easier).Count of messages in queue is there as well, though not exposed.
I intend to create a small REST API that would allow you to plug into this as well. I would gladly accept any contribution that you can think of. For myself, I think that one major contribution would be just a viewer app, to aid in debugging what is going on. On Thu, Apr 2, 2009 at 12:13 AM, Corey Kaylor <[email protected]> wrote: > I'm really liking this direction. Another question if you have time. > > MSMQ administration is a pain. Do you plan to add administrative functions > into the api? For instance, if I want to build a replacement for the MSMQ > administration utility, will this be directly possible for both local and > remote administration? > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
