Changes between Version 5 and Version 6 of MsXBrain


Ignore:
Timestamp:
09/19/06 11:27:52 (12 years ago)
Author:
ebmoore
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MsXBrain

    v5 v6  
    2929 1. Because of #1, I have to encode the results or the query into a URL (I opted for the query using Base64 and GZip). 
    3030 
    31 To accommodate this, it takes the query as the post and then uses a distributed XQuery to get the results and process them when they are requested by MindSeer. 
     31To accommodate this, it takes the query as the post and then uses DXQP to get the results and process them when they are requested by MindSeer. 
    3232 
    3333== How it fits in == 
     
    3535http://sig.biostr.washington.edu/~ebmoore/MindSeerXBIntegration2.png 
    3636 
    37 While this diagram captures the XBrain System fairly accurately (with some simplification and completely leaving off the 2D image view), it fails to show how things are connected.  Conceptually, you can imagine distributed XQuery (dxquery) binding the system together.  Currently, there is no centralized server or library that does dxquery, but instead each component can use its own dxquery engine (unfortunately each engine has its own syntax).  In this case, MindSeer is integrated using AngloSaxon and the other components are integrated using a degenerate form of dxquery (just shipping the query and getting a document). 
    38  
     37While this diagram captures the XBrain System fairly accurately (with some simplification and completely leaving off the 2D image view), it fails to show how things are connected.  Conceptually, you can imagine distributed XQuery (dxquery) binding the system together.  DXQuery is not being done by DXQP using AngloSaxon.  As you can see in the image below, DXQuery (via DXQP) is what binds the whole system together on the backend and the XBrain portal is just the opening page. 
    3938http://sig.biostr.washington.edu/~ebmoore/MindSeerXBIntegration.png 
    4039 
     
    4443 
    4544http://sig.biostr.washington.edu/~ebmoore/User_Clicks_3D_Button.png 
     45''This image is slightly out of date'' 
    4646 1. The XBrain User clicks on the 3D button and posts the XQuery to MsXBrain. 
    47  1. The XQuery is encoded and placed in the MindSeer launching file (JNLP file) as a URL 
     47 1. An intermediate page allows the user to select a patient. 
     48 1. The patient id, whether to use client/server and XQuery is encoded and placed in the MindSeer launching file (JNLP file) as a URL 
    4849 1. The JNLP file is returned to the XBrain User. 
    4950 
    5051http://sig.biostr.washington.edu/~ebmoore/Request_Map_File.png 
     52''This image is slightly out of date'' 
    5153 1. MindSeer uses the URL to request a map file (Results.bmx?...) 
    5254 1. Tomcat sends the file to the MindSeer File servlet. 
    5355 1. MindSeer File requests the data using the encoded query. 
    54  1. AngloSaxon executes the query on the XCSM and TransformationServer 
    55  1. The resuls are returned to MindSeer to display to the user. 
     56 1. AngloSaxon and DXQP execute the query on the XCSM and TransformationServer 
     57 1. The results are returned to MindSeer to display to the user. 
    5658 
    5759== Distributed XQuery ==