Archives access should probably be by files about citra HOT 4 CLOSED

Random note: The fix for this issue might also want to address: #192 (comment)

from citra.

I think Archives and Files should still be separate objects, however, I think the big issue in our impl is that, for some reason, Archive implements a full File-like interface. File reading/writing operations don't belong in Archive and should be moved to File instead. Archives shouldn't be readable or writable. Another complaint I have with the current implementation is that the file ops are done via SyncRequest, and there's no good reason for this. That method is intended to dispatch behavior of the corresponding syscalls, which isn't related in this case, since users can't even pass FS service handles to that kernel function. (They're not kernel objects and they're 64-bit instead of 32-bit.) Archives and files should also not be implemented as kernel objects as they currently are, since in the real system they live in a completely separate object pool inside the FS service.

from citra.

This has been mostly fixed by #283. I think we can close it.

from citra.

Indeed. Closed.

from citra.