> They still retain SFS as a requirement for implementing a shared logging > facility for the SMAPI servers, so none of that complexity is alleviated.
Ugh. Well, that frankly sucks. Having simple UIs depend on one of the more complicated CMS features seems suboptimal in just about every way I can think of, especially with all the other choices available for reasonable logging methods. > I > suspect that the SFS based queuing had to be based on polling for a > communications file, where the writable segment based CMSMT-IPC driver can > use external interrupts instead of polling. (CMS multitasking allows > transport services for inter-process communications to be added through a > programming interface. It comes with IUCV or APPC, and folks have written > other transport drivers for TCP and now writable segments. Would also make sense. As I said, just a guess on my part. I don't claim to know the Mind of Alan. > Worse than the fact that the NAMESAVE record is inserted dynamically, is > the > fact that it's all a secret. Want me to write a requirement? I seem to be becoming the designated CMS requirements submissions dude via WAVV...8-) -- db
