IMServer: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 24: | Line 24: | ||
== Using multiresolution data == | == Using multiresolution data == | ||
== Using browser based client == | |||
* The implementation can be better understood with [[IMServer:Demos | demos]] | |||
* Implementation of [[IMServer:WebClient]] | |||
== Using desktop application == | |||
* | * Accessing MongoDB directly | ||
* | * Accessing using a webserver | ||
== Useful References == | == Useful References == | ||
Latest revision as of 17:38, 5 April 2011
Why Image Server
- Format neutral representation. A Standard API to view and manipulate the data at desired extent and resolution
- Though it is possible to access any image with multiresolution, especially the formats liKE JPEG 2000 or ndpi, the processing takes time, and not always suitable for web sevice
Hosting an image server
Current dependencies to
- A database capable of storing binary objects
- A webserver currently Apache2, if the data needs to be accessed remotely (note it is also possible to directly connect to a database remotely.
- Server side code to fetch images from database on demand
Adding large image set to the server
- | VTK
- VTKMicroscopy / VTKPers, libraries extending VTK (Developed at Kiware)
- 64bit C++ driver for MongoDB database
- An uploading script Implementation for dir_uploader
Using multiresolution data
Using browser based client
- The implementation can be better understood with demos
- Implementation of IMServer:WebClient
Using desktop application
- Accessing MongoDB directly
- Accessing using a webserver
