This is a continuation of a previous conversation (http:// groups.google.com/group/rhino-tools-dev/browse_thread/thread/ d1ec9838788be43f) the focus of which has shifted enough to merit a new thread.
So I am now looking at adding performance counters to Rhino-Queus. Again my intention is to keep it simple to start with and add features as needed. I am envisioning two categories named "Rhino-Queues Outbound" and "Rhino-Queues Inbound." Initially each will have one NumberOfItems32 counter named "Unsent Messages" and "Arrived Messages" respectively. Outbound instances will be per URI to which messages are being sent and named accordingly. Inbound instances will be per port + queue name. Currently my design calls for adding events to IQueueManager interface that are raised each time a message is added to or removed from an inbound or outbound queue; with the performance counter code hooking into these events and updating the counts appropriately. Each time a QueueManager is initialized, the counter's values will be synced with the counts from persistent storage. Comments? -- 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.
