From my limited understanding, the semantics of what the application is doing when it "sends an instruction to the Fujinet" are very like the semantics of dealing with files. So for me, Fujinet offering a filing system is not just a case of it offering a remote fileservice.
Acorn filesystems commonly have the idea of drives. It seems to me moderately natural for one drive to be, say, the remote filesystem, and another drive to be, say, an HTTP interface.
I haven't seen (or haven't remembered) a simple tabulation of the sorts of things an application or user might want to do with Fujinet. I'd be trying see how those actions could sensible map onto MOS calls, or filing system actions, or command line actions, or some mixture.
I'd be disappointed if there was very much by way of a new ABI - I expect the existing interfaces will be enough, if we can get across the communication gap, between Fujinet experts and Acorn experts.
Acorn filesystems commonly have the idea of drives. It seems to me moderately natural for one drive to be, say, the remote filesystem, and another drive to be, say, an HTTP interface.
I haven't seen (or haven't remembered) a simple tabulation of the sorts of things an application or user might want to do with Fujinet. I'd be trying see how those actions could sensible map onto MOS calls, or filing system actions, or command line actions, or some mixture.
I'd be disappointed if there was very much by way of a new ABI - I expect the existing interfaces will be enough, if we can get across the communication gap, between Fujinet experts and Acorn experts.
Statistics: Posted by BigEd — Thu Sep 05, 2024 6:23 pm