Context Navigation

Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Changes between Version 4 and Version 5 of Ticket #4026

Timestamp:: 01/28/11 13:05:53 (13 years ago)
Author:: atarkowska
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #4026 – Description

-                      v4
+                      v5
 '''How image zoom technology works?'''
 The most efficient way to provide high resolution imaging on the web can be achieved by making an "image pyramid" out of the source image and cut it into small tiles. Whenever the user requests a portion of the image only the needed tiles of a level are sent to the client's browser. However, since this tiles are loaded by the client's browser or can be accessed over http, they can be easily reassembled (stitched back together), thus restoring the entire original image.
+The most efficient way to provide high resolution image on the web can be achieved by making an "image pyramid" out of the source image and cut it into small tiles. Whenever the user requests a portion of the image only the needed tiles of a level are sent to the client's browser. However, since this tiles are loaded by the client's browser or can be accessed over http, they can be easily reassembled (stitched back together), thus restoring the entire original image.
 Instead of sending the tiles directly to the browser it could put them first together on the server side and only then send the requested portion as one picture to the client. Neither the tiles nor the original image are ever loaded by the client.
+Instead of sending the tiles directly to the browser it could put them first together on the server side and only then send the requested portion as one picture to the client. Neither the tiles nor the original image are ever loaded by the client. Optionally could crop from the original image without making the tiles.
  - http://www.ajax-zoom.com/