[Home] [Groups] - Message: [Prev in Group] [Next in Group]

nu.kanga.list.mud-dev

16581: Re: Re[2]: [MUD-Dev] Modular Design Issues RFC

[Full Header] [Plain Text]
From: "Ryan Rhodes" <ryanshaerhodes@hotmail.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Mon, 12 Mar 2001 22:15:34 -0800
References: [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] <-newest
Organization: Kanga.Nu
>  Kwon Ekstrom wrote:

> Output is non-blocking in the sense that it always returns in a
> short amount of time, what I'm talking about by non-blocking is the
> fact that I check for data in the input stream before pulling from
> it.  The read methods in java will block the thread until the stream
> receives enough data for it to return.  

Let's say I put my data backend on another machine on the local
network and do periodic saves of the whole game out to the database.
If I just wrote the entire game object (the whole runtime basically)
out to that other machine with an Object Output Stream can I still
consider that a short ammount of time?  Is the delay for writing
output proportional to the size of the output?  Also, is this delay
unrelated to weather its written over a network or to the local disk
on a separate thread?

Ryan Rhodes
_______________________________________________
MUD-Dev mailing list
MUD-Dev@kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev