walkero
/
openjpeg
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity

added system architecture description on the documentation

This commit is contained in:
Kaori Hagihara 2011-05-25 12:07:39 +00:00
parent b7969ce657
commit dd51c25641
3 changed files with 24 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
applications/jpip/README
View File

@ -53,7 +53,7 @@ Neither the author, nor the university accept any responsibility for any kind of
<Optional> <Optional>
- Xerces2 java XML parser on the client for accessing embedded image metadata (http://xerces.apache.org/xerces2-j) - Xerces2 java XML parser on the client for accessing embedded image metadata (http://xerces.apache.org/xerces2-j)
We tested this software with a virtual server running on the same Linux machine as the clients. Currently, it works only on linux or macosx platforms, windows version should come later. We tested this software with a virtual server running on the same Linux machine as the clients.
---------- ----------
4. Building instructions 4. Building instructions
@ -109,6 +109,7 @@ Client:
Scale up request: Enlarge the window Scale up request: Enlarge the window
ROI request: Select a region by mouse click and drag, then click inside the red frame of the selected region ROI request: Select a region by mouse click and drag, then click inside the red frame of the selected region
<If Xerces2 is installed> <If Xerces2 is installed>
% java -jar opj_viewer_xerces.jar http://hostname/myFCGI JP2_filename.jp2
Annotate image with ROI information in XML metadata: Click button "Region Of Interest" Annotate image with ROI information in XML metadata: Click button "Region Of Interest"
Open a new window presenting an aligned image with a locally stored image: Click button "Image Registration" (Under Construction) Open a new window presenting an aligned image with a locally stored image: Click button "Image Registration" (Under Construction)

BIN
applications/jpip/doc/jpip_architect.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 62 KiB

30
applications/jpip/mainpage.h
View File

@ -64,14 +64,28 @@
* *
* *
* \section sysarchtect System Architecture * \section sysarchtect System Architecture
* JPIP protocol is implimented between the server program opj_server and the client java program opj_viewer.\n * JPIP protocol is implimented between the JPIP server program (opj_server) and the JPIP client java program (opj_viewer).\n
* The opj_server parses JPIP requests and sends corresponding JPT-stream. * Figure below represents the overview of our system architecture.\n
* The opj_viewer is an image viewer with GUI to publish JPIP requests and receive JPT-stream.\n * The JPIP server parses JPIP query and sends corresponding JPT-stream.
* JPT-stream is unreadable for the opj_viewer by itself, and the local server program opj_dec_server handles the decoding and caching of JPT-stream.\n * The JPIP client viewer is an image viewer with GUI to publish JPIP requests and receive JPT-stream.\n
* Typical requests and replies among JPIP server (opj_server), JPIP client (opj_viewer), and Image decoding Server (opj_dec_server) is presented below.\n * Particularly, our system has the image decoding module implemented on a server (opj_dec_server, Image decoding Server).
* The JPIP client requests the JPIP server JPT-stream, which is directly sent to the Image decoding Server, and which provides the image in PGM or PPM format to the JPIP client.\n * Image decoding Server and JPIP client viewer communicate closely.
* JPIP client can read PGM and PPM images natively.\n * This specific architecture enables sharing cache of image codestream data among all viewers connected to the same Image decoding Server not only locally but also remotely.
* Before connecting to the JPIP server, the JPIP client checks local cache data of the requesting image with the image decoding server. *
* \image html jpip_architect.png "OpenJPIP system architecture"
*
* JPIP server follows up the client cache during a session. \n
* Concretely, the JPIP server models cache in each session, to which Channel IDs are associated.
* A Channel ID identifies a JPIP client viewer.
* And, new viewers can belong to a session by referring to one of its channel ID.
* The Image decoding Server maintains the association between channel IDs and targets, and provides a reference channel ID to a Viewer on demand.\n
*
* Typical requests and replies among JPIP server, JPIP client, and Image decoding server is presented below.\n
* The JPIP server parses HTTP query and sends corresponding JPT-stream back to the JPIP client (Viewer).
* JPT-stream is unreadable by JPIP client, and it is directly passed to Image decoding Server, and which provides the image in raw format (PGM or PPM) to the JPIP client.
* The Image decoding Server handles the decoding and caching of JPT-stream.
* JPIP client can read PGM and PPM images natively.
* Before connecting to the JPIP server, every JPIP client checks local cache data of the requesting image with the image decoding server.
* If its cache exists, the image decoding server provides ChannelID (CID), which identifies the image and its cache model on the JPIP server, and the whole system can continue the session using the CID. * If its cache exists, the image decoding server provides ChannelID (CID), which identifies the image and its cache model on the JPIP server, and the whole system can continue the session using the CID.
* *
* \image html jpip_protocol.png "Message Sequence Chart of OpenJPIP impementation" * \image html jpip_protocol.png "Message Sequence Chart of OpenJPIP impementation"