Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
LabComm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Sven Gestegård Robertz
LabComm
Commits
88bfe766
Commit
88bfe766
authored
11 years ago
by
Sven G. Robertz
Browse files
Options
Downloads
Patches
Plain Diff
added a bit on library structure
parent
e5d36a8c
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/tech_report.tex
+41
-4
41 additions, 4 deletions
doc/tech_report.tex
with
41 additions
and
4 deletions
doc/tech_report.tex
+
41
−
4
View file @
88bfe766
...
...
@@ -144,13 +144,50 @@ only arrays of arrays.
sample user
_
type another
_
user
_
type
_
instance;
\end{verbatim}
\section
{
User actions
}
\section
{
The LabComm system
}
User actions (similar to ioctl()) allowing the application or a higher level
The LabComm system consists of a compiler for generating code from the data
descriptions, and libraries providing LabComm communication facilities in,
currently, C, Java, Python, and C#.
\subsection
{
The LabComm compiler
}
\subsection
{
The LabComm library
}
The LabComm libraries contain functionality for the end-to-end transmission
of samples. They are divided into two layers, where the upper layer implements
the general encoding and decoding of samples, and the lower one deals with
the transmission of the encoded byte stream on a particular transport layer.
Thus, the LabComm communication stack looks like this:
\begin{verbatim}
_______________________
| Application |
+---------------------+
| encoder | decoder | to/from labcomm encoded byte stream
+----------+----------+
| writer | reader | transmit byte stream over particular transport
+----------+----------+
| transport layer / OS|
+---------------------+
\end{verbatim}
\subsubsection
{
LabComm actions
}
(similar to ioctl())
The encoder/writer and decoder/reader interfaces consist of a set of actions
One example of this is that there is a a separate writer action for
transmitting signatures, allowing the writer to treat a signature differently
from encoded samples, e.g., to allow handshaking during channel setup.
User actions allow the application or a higher level
protocol to communicate with the underlying transport layer through the LabComm
encoder A special case of this is a specific action informing the underlying
transport that a signature is being sent (to allow handshaking)
encoder.
One example is reliable communication, which is controlled from the application
but needs to be implemented for each transport at at the reader/writer level.
(Or not, e.g., TCP)
\section
{
LabComm is not...
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment