Browse Prior Art Database

METHOD OF POLLING MULTIPLE DEVICES WITH LIMITED RESOURCES, WHIL E ENSURING THE TIMELINESS OF DEVICE STATUS POLLING THREAD SCHEDU

IP.com Disclosure Number: IPCOM000013508D
Original Publication Date: 1999-Dec-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 2 page(s) / 28K

Publishing Venue

IBM

Related People

Dennis Carney: AUTHOR [+2]

Abstract

Disclosed is a method for a monitoring application to monitor multiple devices without having to use one thread per device, while still ensuring timely status. The basic method is to use one controller thread, the "polling thread scheduler" thread, that controls some number of polling ("polling" means sending queries at

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

  METHOD OF POLLING MULTIPLE DEVICES WITH LIMITED RESOURCES, WHIL E ENSURING THE TIMELINESS OF DEVICE STATUS POLLING THREAD SCHEDU

   Disclosed is a method for a monitoring application to monitor multiple devices
without having to use one thread per device, while still ensuring timely status.
The basic method is to use one controller thread, the "polling thread scheduler"
thread, that controls some number of polling ("polling" means sending queries at
constant time intervals--every 30 seconds, for example) threads. These polling
threads might be of different type; for example, one type of thread might poll
every 30 seconds for a lot of information, while another type might poll every 5
seconds for one simple piece of information. This method makes it such that when
monitoring a large number of devices, the number of polling threads would be much
smaller than the number of devices.

Requests for polling a device would be sent to the
scheduler, passing in the type of polling required.
The scheduler would then determine whether there
were any running threads of the desired polling
type that could handle the request. If an
available thread was found, the scheduler would add
the device to that thread's device list.
Otherwise, if no thread of the right type was
running, or if all running threads of the right
type were too busy, a new thread would be started.

The scheduler waits on polling requests, but if no
requests arrive for a specified time, it would wake
up in order to check its current se...