Hi, In looking at implementing some aspects of SSC in concert with MMC, and especially considering things like MAM and even how to handle things like FILE marks and GAPs etc, it seems to me that one model to use would be to have a separate file for certain things, or even a database of sorts that keys off of a token associated with a slot. One way to more flexibly support this would be to have the struct device_type_template have separate backed_file_open and backed_file_close methods andto call these from dtd_load_unload. If the particular device is happy with the default backed_file_open request, it could simply initialize its device_type_template with this function, otherwise it could override the default with its own implementation ... Does anyone have any comments on this? -------------- next part -------------- An HTML attachment was scrubbed... URL: https://lists.berlios.de/pipermail/stgt-devel/attachments/20080703/5d6a3fd0/attachment.html |