Re: [Fresco-devel] [ReFresco 03] Proposed network architecture overview

On Mon, Feb 02, 2004 at 08:56:40PM +0100, [email protected] wrote:
> > > Your DOS scenario isn't a problem either.
> > 
> > I still think it is: Lets assume there are two object A and B in the same
> > client. They share one connection to the server. A can now block that
> > connection for long times by sending huge messages (the max. message length
> > takes several days to go over a 100MBit network). B can't send data to the
> > server during that time.
> do we have _one_ tcp-connection per client to the server? in this case messages
> can processed in paralel i think. so other messages (to and from the server)
> can send without limitation.

Not quite following this.  I am very, very hesitant to encourage
clients to make multiple connections during normal operation; this is
ugly, may cause havoc with server memory management (the server tracks
object allocation by connection, so it can clean up when connections
go away), and just makes everything more complicated.

You do need some sort of managed multiplexing in some cases to avoid
congestion and apply backpressure, but I think we can best manage this
at a higher level.

> or is caprice not a client/server-architecture?

Huh?

-- Nathaniel

-- 
When the flush of a new-born sun fell first on Eden's green and gold,
Our father Adam sat under the Tree and scratched with a stick in the mould;
And the first rude sketch that the world had seen was joy to his mighty heart,
Till the Devil whispered behind the leaves, "It's pretty, but is it Art?"
  -- The Conundrum of the Workshops, Rudyard Kipling