A collaboration between Ed Rantanen and myself to provide basic visualization of a trace route in a flexible manner. This should allow the swapping of different graphic libraries such as Graphviz, Flot, etc.
bmallred
0e354509da
moved files from bitbucket
|
12 ans auparavant | |
|---|---|---|
| .. | ||
| Properties | 12 ans auparavant | |
| BlockType.cs | 12 ans auparavant | |
| MIT.txt | 12 ans auparavant | |
| Parser.cs | 12 ans auparavant | |
| ParserToken.cs | 12 ans auparavant | |
| README.txt | 12 ans auparavant | |
| TextBlock.cs | 12 ans auparavant | |
| VisualTraceRoute.Text.csproj | 12 ans auparavant | |
| sample-console.txt | 12 ans auparavant | |
| sample-xml.txt | 12 ans auparavant | |
README.txt
Author: Bryan M. Allred
Last update: 6/5/2011
The intentions of the Parser is to allow users to change the data structure
without needing to recompile the source code. This may also aid in the
flexibility to allow swapping of graphing utilities.
Available tokens are:
{destination}
{address}
{hop}
{hostname}
{roundtrip}
Also, understanding there will be multiple replies on any given trace there
has to be a way to mark repeating text. This is done with the following
text:
{routes}
{hops}
{/hops}
{/routes}
Some times there needs to be a separator between iterations:
{routes}
{/routes},
or
{routes}
{hops}
{/hops},
{/routes}
Last update: 6/5/2011
The intentions of the Parser is to allow users to change the data structure
without needing to recompile the source code. This may also aid in the
flexibility to allow swapping of graphing utilities.
Available tokens are:
{destination}
{address}
{hop}
{hostname}
{roundtrip}
Also, understanding there will be multiple replies on any given trace there
has to be a way to mark repeating text. This is done with the following
text:
{routes}
{hops}
{/hops}
{/routes}
Some times there needs to be a separator between iterations:
{routes}
{/routes},
or
{routes}
{hops}
{/hops},
{/routes}