Author: zurawski Date: 2010-01-15 07:20:22 -0600 (Fri, 15 Jan 2010) New Revision: 9 Modified: extension.tex nmc-base.pdf Log: Fixing a 'bug' where the line was not being broken properly by tex. -jason Modified: extension.tex =================================================================== --- extension.tex 2010-01-13 15:26:40 UTC (rev 8) +++ extension.tex 2010-01-15 13:20:22 UTC (rev 9) @@ -462,7 +462,7 @@ \paragraph{eventType Extension} \label{s:echo_protocol_extension_eventtype} -The current accepted eventType for the \textit{Echo Protocol}'s \textbf{EchoRequest} message is \textbf{http://schemas.perfsonar.net/tools/admin/echo/2.0}. This \textit{action} \textbf{MUST} be accepted by all services. By adding additional eventTypes with the same format it is possible to extract additional information via a service. +The current accepted eventType for the \textit{Echo Protocol}'s \textbf{EchoRequest} message is \\ \textbf{http://schemas.perfsonar.net/tools/admin/echo/2.0}. This \textit{action} \textbf{MUST} be accepted by all services. By adding additional eventTypes with the same format it is possible to extract additional information via a service. Consider simple service X. The designer of this service wishes to create a special behaviour for specific eventTypes. The following new eventTypes are added to her service code (and to her implementation of the schema): Modified: nmc-base.pdf =================================================================== (Binary files differ)