Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Z
zmap
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ensembl-gh-mirror
zmap
Commits
a14e1d2a
Commit
a14e1d2a
authored
15 years ago
by
edgrif
Browse files
Options
Downloads
Patches
Plain Diff
commit what I've done up until now.
parent
02a38e25
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
web/user_doc/xremote/xremote_overview.shtml
+86
-3
86 additions, 3 deletions
web/user_doc/xremote/xremote_overview.shtml
with
86 additions
and
3 deletions
web/user_doc/xremote/xremote_overview.shtml
+
86
−
3
View file @
a14e1d2a
...
...
@@ -39,6 +39,30 @@ possible.
<br />
<fieldset>
<legend>The <code>xremote_gui</code> Tool</legend>
<p>ZMap provides a test application for testing the protocol and this
section describes how to run the tool.</p>
<p>Edit the .ZMap config file and make sure the "default_sequence" keyword
is commented out:
<p><b>1) Start the tool:</b>
./xremote_gui --no_timeout --sequence=b0250 ./zmap 2>&1 tee xremote_out.txt
</fieldset>
<br />
<fieldset>
<legend>Stuff that needs sorting out.....</legend>
...
...
@@ -116,6 +140,65 @@ I propose this is changed to:
<fieldset>
<legend>ZMap Client Communication Protocol</legend>
<p><i>(See UML "Sequence" Diagram for description of diagram syntax.)</i></p>
<p>The Protocol is a peer-to-peer asynchronous "Request - Response" protocol. That is:</p>
<ul>
<li><b>All</b> Requests must be replied to with a Response.
<li>Either side may send a Request at any time.
<li>The Response to a Request will come up to "timeout" seconds later, if no
Response arrives then the peer should send a "timeout" exception.
<li>It is an error to send a second Request before receiving the Response
to the first Request.
</ul>
<p>The normal request sequence will be:
<img src="./request_response.png" align="center">
</p>
<p>
<img src="./request_response2.png">
</p>
<p>with the transmitted xml being:
<pre class="request">
<zmap>
<request>
request body
</request>
</zmap>
</pre>
<pre class="response">
<zmap>
<response>
response body
</response>
</zmap>
</pre>
</p>
</fieldset>
<br />
<fieldset>
<legend>Otterlace chain of events</legend>
...
...
@@ -179,7 +262,7 @@ understands.
<action>close</action>
</client>
</response>
<meta display="localhost:10.0" windowid="0x2c00004" application="" version="$Revision: 1.
1
$" />
<meta display="localhost:10.0" windowid="0x2c00004" application="" version="$Revision: 1.
2
$" />
</zmap>
</pre>
...
...
@@ -295,7 +378,7 @@ tables fit in.
<meta display="localhost:10.0"
windowid="0x2c00004"
application=""
version="$Revision: 1.
1
$" />
version="$Revision: 1.
2
$" />
</zmap></pre>
</td>
</tr>
...
...
@@ -416,7 +499,7 @@ featuresets = "Coding Repeats BLASTX"
<meta display="localhost:10.0"
windowid="0x2c00084"
application=""
version="$Revision: 1.
1
$" />
version="$Revision: 1.
2
$" />
</zmap></pre></td>
</tr>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment