Garrett D'Amore wrote: > You also need to have values that are persistent -- i.e. the driver > could detach (e.g. due to idleness), and when it gets reloaded later > (perhaps because it was now being used) you want to use the same values > it had before. This means that you really need a pull rather than a > push mechanism.
Hmm. You need both, because you need to allow the administrator to change things. (Of course, that could be either bidirectional push/pull, or notifications in one direction plus push or pull in the other. Perhaps, for instance, the reattach might cause a notification that would cause the setup application to run.) > I am confident that I could invent my own subsystem to make this work. > I'm just not confident that inventing yet another wheel is a good idea. It's usually not. The question is which existing wheel is the best match, and then convincing the people who are attached to that wheel that it should be used for your purpose too.
