IMServer: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
| Line 24: | Line 24: | ||
* The implementation can be better understood with demos | * The implementation can be better understood with demos | ||
** Demo | ** Demo [http://dash1old/connectome/index2.php?image=z3459 | from Kitware network] | ||
** Demo | ** Demo [http://tripoint.kitware.com/connectome/index2.php?image=z3459 | from outside] | ||
* Viewer for Jeff's data | |||
** [http://dash1old/connectome/daniels.php | from Kitware network] | |||
** Demo [http://tripoint.kitware.com/connectome/daniels.php | from outside] | |||
* Implementation of [[IMServer:WebClient]] | * Implementation of [[IMServer:WebClient]] | ||
Revision as of 20:24, 14 February 2011
Hosting an image server
Current dependencies to
- A database capable of storing binary objects
- A webserver currently Apache2
- 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 (very difficult to compile with windows)
- An uploading script Implementation for dir_uploader
Using multiresolution data
= Development of a browser based client
- The implementation can be better understood with demos
- Demo | from Kitware network
- Demo | from outside
- Viewer for Jeff's data
- Implementation of IMServer:WebClient
