Trajectory-client: Difference between revisions

Trajectory-client (view source)

Revision as of 09:20, 4 July 2018

245 bytes added , 4 July 2018

no edit summary

Maintenance script

176

edits

@@ Line 2: / Line 2: @@
 Navigation: [[Documentation]] / [[Commands]] / [[trajectory-client]]
 ----
-<div style="text-align: center">trajectory-client: version 2.203.4878adb(2018-07-03 23:15) [CATs - Conversion And Analysis Tools]</div>'''Name'''
+<div style="text-align: center">trajectory-client: version 2.204.c62bd73(2018-07-04 10:11) [CATs - Conversion And Analysis Tools]</div>'''Name'''
 <span style="margin-left: 15px;">trajectory-client</span>
@@ Line 18: / Line 18: @@
 {| style="margin-left: 2em; width: 95%;"
 |- style="vertical-align: top; background-color: #e6e6e6;"
-| <span style="color: purple;">trj://server[:port]/command</span><br/><div style="margin-left: 30px;">specifies fully qualified administration request. Trasport protocol cats:// has to be always specified. It is followed by server parameter which could be either DNS name or IP address of server. Optional port parameter is port number used in a communication. Finally, the command is a task, which can be one of the following:<br /><span></span>   register   = register client on server side<br /><span></span>   unregister = unregister client on server side (unregister?id=client_id)<br /><span></span>   getcrd     = get coordinate snapshot (getcrd?id=client_id,topology=file1.top,coords=file2.crd)<br /><span></span>   getvel     = get velocities (getvel?id=client_id,topology=file1.top,coords=file2.crd)<br /><span></span>   info       = prints information about registered clients<br /><span></span>   shutdown   = stops server execution<br /><span></span>   errors     = prints errors from server stack<br /></div>
+| <span style="color: purple;">trj://server[:port]/command</span><br/><div style="margin-left: 30px;">specifies fully qualified administration request. The trasport protocol trj:// has to be always specified. It is followed by a server parameter, which could be either DNS name or IP address of server. Optional port parameter is port number used in a communication. Finally, the command is a task, which can be one of the following:<br /><span></span>   <span style="color: green;">register</span>   = register client on server side<br /><span></span>   <span style="color: green;">unregister</span> = unregister client on server side (unregister?id=client_id)<br /><span></span>   <span style="color: green;">getcrd</span>     = get coordinate snapshot (getcrd?id=client_id,topology=file1.top,coords=file2.crd)<br /><span></span>   <span style="color: green;">getvel</span>     = get velocities (getvel?id=client_id,topology=file1.top,coords=file2.crd)<br /><span></span>   <span style="color: green;">info</span>       = prints information about registered clients<br /><span></span>   <span style="color: green;">shutdown</span>   = stops server execution<br /><span></span>   <span style="color: green;">errors</span>     = prints errors from server stack</div>
 |}