-
Notifications
You must be signed in to change notification settings - Fork 10
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.
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
FEO: Feature request #294
base: main
Are you sure you want to change the base?
FEO: Feature request #294
Conversation
44ed1e4
to
7df5237
Compare
This currently has 24 changed files. I assume that's not intentional? |
Thanks for the hint. Fixed.
CONFIDENTIAL
From: Alexander Lanin ***@***.***>
Reply to: eclipse-score/score ***@***.***>
Date: Thursday, 6. February 2025 at 20:06
To: eclipse-score/score ***@***.***>
Cc: Markus Bechter ***@***.***>, Author ***@***.***>
Subject: Re: [eclipse-score/score] FEO: Feature request (PR #294)
Sent from outside the BMW organization - be CAUTIOUS, particularly with links and attachments.
Absender außerhalb der BMW Organisation - Bitte VORSICHT beim Öffnen von Links und Anhängen.
…________________________________
This currently has 24 changed files. I assume that's not intentional?
—
Reply to this email directly, view it on GitHub<#294 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVHJZKOTPNO7F2MMAEKMVSD2OOXDBAVCNFSM6AAAAABWUAETDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBQG42TOMRVGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Also-by: aschemmel-tech
as the strucure of the metamodel has changed also the existing content needs to be adapted
Use sphinx-autobuild to implement live preview without requiring VSCode integration. This allows previewing on save independent of IDE. Signed-off-by: Nicolae Dicu <[email protected]>
Initial commit of feature request
* There are two types of activities: | ||
- Application activities | ||
- Service activities | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe, add a headline here as well?
Application Activities | |
============== |
Co-authored-by: olivembo <[email protected]> Signed-off-by: ramceb <[email protected]>
relies on the message itself independent of the source of the message | ||
* There can only be one sender per topic but multiple receivers | ||
* Optional: there can be multiple senders per topic | ||
* There is no publish/subscribe mechanism acessible to activities, instead |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo
* There is no publish/subscribe mechanism acessible to activities, instead | |
* There is no publish/subscribe mechanism accessible to activities, instead |
queue by a receiver doesn't change the queue, i.e. doesn't remove it from the queue. | ||
instead all receiver will always see the last N elements | ||
* Optional: a queue pointer to the element last read is maintained per receiver. | ||
however, the queue with its buffers still only exists once per topic. if one receiver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
however, the queue with its buffers still only exists once per topic. if one receiver | |
However, the queue with its buffers still only exists once per topic. If one receiver |
Provides a proposal for a communication framework feature.