Paul,
I have given this some thought for another reason. This is a fundamental
change in the model, since you actually need to configure the pseudodevices
rather than discover them.
The best idea I have right now is that you need a directory called
synthesized, pseudodev or similar.
For this idea, you would need to define an extensible config file format
and parsing, that can collect the needed information and make it available.
Then you need to set up some kind of callback scheme with the name selected
from the config. There needs to be a defined set of functions and naming
conventions, since this is C code in general.
For each pseudodevice, the user names it and it gets put in a directory
defined by the callback under the top level name you choose. It would be up
to the callback/you as to whether the true devices shows up anywhere else.
jerry
Jerry Scharf
laguna way consulting
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
