Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Proposed texts for initialization, closure of HTTPS and merged signal discovery read with dynamic metadata read on HTTPS parts #485

Merged
merged 4 commits into from
Sep 27, 2023
Merged

Proposed texts for initialization, closure of HTTPS and merged signal discovery read with dynamic metadata read on HTTPS parts #485

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
fa56694
Propsed texts for initialization and closure of HTTPS
wonsuk73 Sep 5, 2023
6054fe3
Merge signal discovery read with dynamic metadata read on HTTPS
wonsuk73 Sep 5, 2023
a8011ea
Revised texts to fix the "www" prefix concern
wonsuk73 Sep 6, 2023
02a76ba
Fixed the conflict sentence
wonsuk73 Sep 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 16 additions & 8 deletions spec/VISSv2_Transport.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -321,12 +321,25 @@ <h2>Session Life Time Management</h2>

<section id="https-initialisation">
<h2>Initialization</h2>
<p>HTTP long polling?</p>
<p>Initialization involves setting up a secure HTTPS session between the client and the server.
This ensures encrypted communication for data transmission.
To initialize a secure session, the client sends a request to the server using the HTTPS protocol.
This is achieved by connecting to the server's designated URL using the 'https://' scheme.
The client can use a web browser, a native application, or a suitable library in the case of programmatically managed sessions.<br>
While the client typically connects to the server using the specified hostname, which often includes the "www" prefix,
it's important to note that this convention may not apply in situations where VISS operates within a local, in-vehicle network or if remote vehicle connections are allowed.
The communication typically takes place over port 443, the default port for secure HTTPS connections.
The hostname resolution can be done via DNS or configured through local settings.
</p>
</section>

<section id="https-closure">
<h2>Closure</h2>
<p>HTTP long polling?</p>
<p>Closure entails ending the established HTTPS session when the communication is complete or when the client no longer requires the connection.
Either the client or the server can initiate the session closure. The client can signal the end of the session by sending an appropriate request to the server,
indicating the intent to close the connection.<br>
Upon session closure, any allocated resources, such as server-side threads or memory, are released, improving overall system efficiency.
</p>
</section>
</section>

Expand Down Expand Up @@ -507,13 +520,8 @@ <h2>Signal Discovery Read</h2>
}
</code></pre>
</p>
</section>

<section id="https-dynamic-metadata-read">
<h2>Dynamic Metadata Read</h2>
<p>
The dynamic metadata, i. e. any other metadata kept by the vehicle system,
is retrieved by the setting the "type" to "dynamic-metadata".
The dynamic metadata, i. e. any other metadata kept by the vehicle system, is retrieved by the setting the "type" to "dynamic-metadata".
The value MUST be set to one of the domain names as specified in the [[viss2-core]], <a data-link-type="dfn" href="https://www.w3.org/TR/viss2-core/#dynamic-metadata-request">Dynamic Metadata Filter Operation</a> chapter.
<br>
<b>Example:</b>
Expand Down
Loading