• Messages sorted by: [ date ][ thread ][ subject ][ author ] [ Next ]
• [ Previous ] In reply to: Justin Mason

> Yep, I'd give a thumbs-up to a client-server scheme too, (a) to deal with
> this issue and (b) to make the system easier to use on a network of many
> client machines talking to 1 repository server.

I'ld already got here, partly as a side effect of needing to deal with replicated servers. NFS has too many error cases, a couple of which have bitten the EROS tree over the years.

The current implementation has a "server switch". At present, there is only one server implementation, which is the "local file system" implementation. There is a second, currently unimplemented interface intended for talking to a server.

A major question is to what degree should the server interface support asynchrony? For example, when the client is fetching a bunch of objects from the server, should it be sending requests and receiving replies simultaneously?

I think the answer is probably yes, though I'm not convinced that this is true over a modem. It used to be the case that modems tried to optimize upstream vs. downstream bandwidth, and the heuristics were pretty bad. How does streaming interact with this?

shap

[ Next ]
• [ Previous ] In reply to: Justin Mason