IMServer: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[category:Connectome]] | [[category:Connectome]] | ||
= Hosting an image server = | == 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 | Current dependencies to | ||
* A database capable of storing binary objects | * A database capable of storing binary objects | ||
** [[IMServer:MongoDB | How to install Mongo]] | ** [[IMServer:MongoDB | How to install Mongo]] | ||
* A webserver currently Apache2 | * A webserver currently Apache2, if the data needs to be accessed remotely (note it is also possible to directly connect to a database remotely. | ||
** [[ IMServer:mod_wsgi | Install mod_wsgi]] | ** [[ IMServer:mod_wsgi | Install mod_wsgi]] | ||
* [[IMServer:Server|Server side code ]] to fetch images from database on demand | |||
[[IMServer:Server|Server side code ]] | |||
== Adding large image set to the server == | == Adding large image set to the server == | ||
* VTK | * [http://www.vtk.org | VTK] | ||
* VTKMicroscopy / VTKPers, libraries extending VTK (Developed at Kiware) | * VTKMicroscopy / VTKPers, libraries extending VTK (Developed at Kiware) | ||
* 64bit C++ driver for MongoDB database | * 64bit C++ driver for MongoDB database | ||
* An uploading script | * An uploading script [[IMServer:Uploader| Implementation for dir_uploader ]] | ||
== 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 == | |||
=== PHP === | |||
* [http://www.php.net/manual/en/mongo.manual.php Manual for PHP Monho driver ] | |||
* [http://www.phpclasses.org/blog/post/118-Developing-scalable-PHP-applications-using-MongoDB.html Developing scalable PHP applications using MongoDB] | |||
=== Python === | |||
* | * [http://api.mongodb.org/python/1.9%2B/tutorial.html Tutorial ] | ||
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
