Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
lmc-base-classes
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
LOFAR2.0
lmc-base-classes
Commits
1816b3ee
Unverified
Commit
1816b3ee
authored
Nov 10, 2021
by
samueltwum1
Browse files
Options
Downloads
Patches
Plain Diff
SAR-277
Reword sentence in design
parent
f8f3810f
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/source/guide/long_running_command.rst
+4
-4
4 additions, 4 deletions
docs/source/guide/long_running_command.rst
with
4 additions
and
4 deletions
docs/source/guide/long_running_command.rst
+
4
−
4
View file @
1816b3ee
...
...
@@ -27,10 +27,10 @@ mechanism to execute long running TANGO commands asynchronously.
Reference Design for the Implementation of Long Running Commands
----------------------------------------------------------------
A message queue solution is the backbone to the implementation of the LRC design. The goal
is to have a hybrid solution which will have the queue usage as an opt in.
Note that the
enqueued commands will block short running commands, reply to attribute reads and writes,
process
subscription requests until completed
with the default option
. That said, the SKABaseDevice
meets the following
requirements for executing long running commands:
is to have a hybrid solution which will have the queue usage as an opt in.
With the default option,
note that the
enqueued commands will block short running commands, reply to attribute reads and writes,
process
subscription requests until completed. That said, the SKABaseDevice
meets the following
requirements for executing long running commands:
* With no queue (default):
* start executing LRC if another LRC is not currently executing
...
...
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