So if I follow, this would involve wrapping Rhino Queues in a separate local service that would then talk to both Rhino-ESB and our theoretical monitoring tool. The down side being that we are getting way from zero configuration at this point. Or I suppose one could build a monitoring API into Rhino-ESB but it would only be available when the bus is actually up an running.
On Feb 9, 9:08 am, Ayende Rahien <aye...@ayende.com> wrote: > SQLite isn't multi user either > The solution is to provide some REST interface on top of Rhino Queues that > would allow a management stuido, ala what we have in RavenDB > > > > > > > > On Wed, Feb 9, 2011 at 4:05 PM, Ken Baltrinic <kbaltri...@gmail.com> wrote: > > We are using Rhino-esb with rhino-queues in a document management > > system where it is working out quite nicely. We are using rhino- > > queues because of the 4 MB message limit in MSMQ doesn't work too when > > sending documents around. However the lack of visibility into the > > queues for system health monitoring purposes is concerning. I see > > this as primarily being a issue with the use of ESENT for storage > > since it is inherently not multi-user. Does anyone see any merit in > > introducing an alternative storage option (say SQLLite?) that would > > permit another process to view the queues while the bus is running? > > What might the cons be? > > > --Ken > > > -- > > You received this message because you are subscribed to the Google Groups > > "Rhino Tools Dev" group. > > To post to this group, send email to rhino-tools-dev@googlegroups.com. > > To unsubscribe from this group, send email to > > rhino-tools-dev+unsubscr...@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/rhino-tools-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to rhino-tools-dev@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
