On Thu, Jan 29, 2004 at 06:34:55PM -0500, Colin Walters wrote:
> First, "why a smart server?". This has been discussed on the mailing
> list in the past, but here's a far-from-exhaustive list of reasons:
BTW, another thing which I think is important is to reduce latency problems
where possible -- current arch remote access methods are _extremely_
latency-bound (it's amazing, even on my butt-slow dialup, arch can only
manage to use about 10% of the bandwidth!).
That is, try to (1) chunk things up (send/get lists of things rather than
one thing at a time), (2) design your protocols so they can be streamed
(instead of a series of short operation-replies, allow a bunch of operations
to be sent as a batch, with well-defined behavior in the case of mid-batch
failure).
Thanks,
-Miles
--
`There are more things in heaven and earth, Horatio,
Than are dreamt of in your philosophy.'