Crossfire Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CF: images & caching.

>>>>[From Mark Wedel]
 ...
     It may not be a bad idea to add various outgoing queues to the server
    - ie, outgoing map queue, outgoing stats queue, outgoing image queue
    (there are others that could be added).  But in the basic example, if
    data to the client is getting backed up, you may only want to send one
    full map update instead of several partial updates. Same for the stats
    - rather than sending 5 stat commands, sending 1 with everything may be
    more efficient.

I haven't looked at the server code TOO much, but I thought it already
did something like this with its server-side "dirty" square checking.
Or is that only used to minimize the amount of data sent with each
update (yet an update is done EVERY time the map is changed)?

If so, then yeah, it would be nice bandwidthwise if the map handling was
USER-TUNABLE to send updates only every X tics
That would be really nice on slow links. but on high-speed links, it's nice
to be able to get things updated as soon as they happen.

Then of course you should have a server-configurable "minimum update limit"
:-)


[to unsubscribe etc., send mail to crossfire-request@ifi.uio.no]
Follow-Ups: References: