regarding structure of the information that is exchanged, which i think Roman asked about. one can conventionally require all fs to provide a control file that when read, returns a dictionary of what the fs can grok. then the messages would follow the dictionary format.
a while ago we had an internal discussion and brucee pointed out that UBF's concepts would be a better choice than xml/xml-schema business. http://www.sics.se/~joe/talks/pittsburgh_2002_ubf.pdf > works well ... my blast room has no wires to the other rooms. > simple p9 box in the corner. wireless audio. and i found the > p9 box on the street. of course i can play a different song from > the studio as well, wireless (well actually it has a telco wire > for when i have to work in mutiple rooms)... > > my wireless laptop can control it all. > > just a few echoes (good song). > > brucee > > On 3/31/06, Skip Tavakkolian <[EMAIL PROTECTED]> wrote: >> >> ioctl(fd, SETVOLUME, &vol); is more comfortable. >> > >> > ah, but how about >> > echo volume 50 >/dev/audioctl >> > for understandability? >> >> i would also add: >> >> import -b noisemaker /dev >> echo volume 50 >/dev/audioctl >> >> please ioctl this!
