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.

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

FEO: Feature request #294

wants to merge 5 commits into from

Conversation

ramceb
Copy link
Contributor

@ramceb ramceb commented Feb 6, 2025

Provides a proposal for a communication framework feature.

@ramceb ramceb force-pushed the mb_fr_feo branch 5 times, most recently from 44ed1e4 to 7df5237 Compare February 6, 2025 16:59
@ramceb ramceb changed the title Mb fr feo FEO: Feature request Feb 6, 2025
@ramceb ramceb marked this pull request as ready for review February 6, 2025 17:42
@AlexanderLanin
Copy link
Member

This currently has 24 changed files. I assume that's not intentional?

@ramceb
Copy link
Contributor Author

ramceb commented Feb 6, 2025 via email

hoe-jo and others added 4 commits February 7, 2025 07:55
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

Copy link

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?

Suggested change
Application Activities
==============

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
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo

Suggested change
* 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
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants