Just creating 1 big image (but small in footprint) and just load that
seems to work best for me. The client then only has to download 1 image
and a tiny img src
-Original Message-
From: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf
Depends on what you call big... you have to take into account the smallest
play size nowadays, like 1024x768 for total, minus the borders... and some
space where some would like to put links in.
From: Erik-jan Riemers riem...@binkey.nl
To: Half-Life dedicated
Hi,
We recently changed to a new bigger/better box.
When RDTSC_FREQUENCY was not set to disabled the server would behave
really strange (speedup lag)
Anyhow, it's now set to disabled but will/can this have any bad
repercussions?
Erik
Note: rdts_frequence was never set.
I use the img solution on my servers and it has been working great so
far. I usually opt for a 8bit PNG with some smart dithering to make it all
smooth and keep the low size.
Recently I've been thinking about switching to a div based layout with
some independant PNGs to make the job of updating
Working fine on my servers.
I load the motd from and URL (motd.txt just contains the URL of the motd
page)
Il 16/05/2012 04:23, Michael Ojeda ha scritto:
A little while I go I sent in an email about HTML MoTDs crashing clients
without an error message, and was told that some javascript files
5 matches
Mail list logo
