Complete.Org: Mailing Lists: Archives: freeciv-dev: June 2002:
[Freeciv-Dev] Re: CMA passes back control without reason (PR#1505)
Home

[Freeciv-Dev] Re: CMA passes back control without reason (PR#1505)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Jason Short <jdorje@xxxxxxxxxxxxxxxxxxxxx>
Cc: freeciv-dev <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: CMA passes back control without reason (PR#1505)
From: Raimar Falke <rf13@xxxxxxxxxxxxxxxxx>
Date: Sun, 2 Jun 2002 23:27:47 +0200

On Sun, Jun 02, 2002 at 02:16:20PM -0400, Jason Short wrote:
> Raimar Falke wrote:
> > On Mon, May 27, 2002 at 12:47:52AM +0200, Raimar Falke wrote:
> 
> >>Yes attributes (which are used by the CMA to store things) currently
> >>get only submit at turn done. It is possible also to submit them at
> >>every change but this wasn't necessary yet.
> > 
> > 
> > Comments? Sending attributes more often will cause more bandwidth
> > usage but will also prevent loss of data if the client
> > aborts/disconnects/crashs.
> 
> Sending attributes only when they change will not necessarily use more 
> bandwidth than sending them every turn.

This is on the long term TODO list.

> Particularly, if we could send a short attribute "update" packet when 
> something changes, this would (almost by definition) be the least 
> bandwidth required, and would also keep the server up-to-date.  I don't 
> know if this is feasible, though.

Since the server doesn't know anything about the internal structure of
the attribute block (it is the serialized hash) such update have to be
in the form "replace data at offset 12 with these 34 bytes".

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
 "Like the ad says, at 300 dpi you can tell she's wearing a
  swimsuit. At 600 dpi you can tell it's wet. At 1200 dpi you
  can tell it's painted on. I suppose at 2400 dpi you can tell
  if the paint is giving her a rash."
    -- Joshua R. Poulson


[Prev in Thread] Current Thread [Next in Thread]