[plc4x-website] branch asf-site updated: Site checkin for project PLC4X: Jenkins Tools

[git-site-role]

This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/plc4x-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 0ec53c5  Site checkin for project PLC4X: Jenkins Tools
0ec53c5 is described below

commit 0ec53c54d6191c607f9ffd3a21fccd07fdf11e8f
Author: jenkins <bui...@apache.org>
AuthorDate: Thu Mar 5 12:18:24 2020 +0000

    Site checkin for project PLC4X: Jenkins Tools
---
 users/plc4j/general-concepts.html | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/users/plc4j/general-concepts.html 
b/users/plc4j/general-concepts.html
index f4aa101..0ec58ec 100644
--- a/users/plc4j/general-concepts.html
+++ b/users/plc4j/general-concepts.html
@@ -367,6 +367,17 @@ This allows them to not only be used in passive-mode 
drivers for simply reading
 <p>The last segment - <code>options</code> - can be used to fine tune some 
protocol or transport options to non-default values. For details on these 
options, please have a look at the <code>Protocol Documentation</code> and the 
<code>Transport Documentation</code>.</p>
 </div>
 <div class="paragraph">
+<p>The general structure of this part is always the same:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>?{option-1-name}={option-1-value}&amp;{option-2-name}={option-2-value}&amp;{option-3-name}={option-3-value}</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>So in general the options are stared with a <code>?</code> and then 
followed by <code>name-value</code> pairs, which are separated by ampersand 
characters <code>&amp;</code>.</p>
+</div>
+<div class="paragraph">
 <p>A driver for a given protocol however usually has a <code>default 
transport</code>, so sometimes it is possible to omit the transport code.</p>
 </div>
 <div class="paragraph">