After trimming down the fat on my ajax calls, I reworked the client-side JavaScript to transform the data into images and links. I even created a method to calculate the difference in weeks, days, hours, minutes, and seconds of when a server was last contacted based on the unix timestamp. In the end, there really isn't a difference to the end-user in what is displayed. I save on both bandwidth and CPU load. For a centralized server, little numbers add up quick. When the load is distributed, everyone wins because it is hardly noticeable on the client. From Dedric Mauriac via <a href="http://bloghud.com" rel="noreferrer nofollow">bloghud.com</a>
Original Details
- Original on Flickr: https://www.flickr.com/photos/dedric-mauriac/4189114607/
Location
- Simulator: Woodbridge
Text Found Within Image
- Name !(DM) PrizeBox 2.1 (1) !(DM) PrizeBox 2.1 (2) !(DM) PrizeBox 2.1 (M) !(DM) PrizeBox 2.1 (Load 1) !(DM) PrizeBox 2.1 (PG Ant 1000) Version Location Items Sdds 1.00B 1.00B 1.00B 1.00B 1.00B Pageview 07_7_200 Pageview 07_7_200 Pageview 07_12_200 Woodbridge 07_12_200 Woodbridge 08_25_200
- taken by : Dedric Mauriac on Woodbridge (8, 2, 99)
- blogHUD!
