Comments

• 

  1 day ago by zbenjamin | Reply

  So as for a protocol there seem to be only a couple of options:

  • sdbus , would be what many service implementations use nowadays but couple us to systemd + dbus. Drawback here is that our minimal container images do not have systemd/dbus running so i'd need to fall back to peer-to-peer mode
  • the libzypp implementation of Stomp, would need a good amount of work to support things peer authentication
  • varlink, a library that is meant for exactly the use case "system services not using dbus"

×
Edit Comment 11637
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
So as for a protocol there seem to be only a couple of options: - sdbus , would be what many service implementations use nowadays but couple us to systemd + dbus. Drawback here is that our minimal container images do not have systemd/dbus running so i'd need to fall back to peer-to-peer mode - the libzypp implementation of Stomp, would need a good amount of work to support things peer authentication - varlink, a library that is meant for exactly the use case "system services not using dbus"
 
×
Reply to zbenjamin
So as for a protocol there seem to be only a couple of options:
• sdbus , would be what many service implementations use nowadays but couple us to systemd + dbus. Drawback here is that our minimal container images do not have systemd/dbus running so i'd need to fall back to peer-to-peer mode
• the libzypp implementation of Stomp, would need a good amount of work to support things peer authentication
• varlink, a library that is meant for exactly the use case "system services not using dbus"
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  1 day ago by zbenjamin | Reply

  Also not available in our minimal images: polkit, this would've been one of the strong points for dbus/system since we'd not need to do authentication ourselves.

×
Edit Comment 11640
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Also not available in our minimal images: polkit, this would've been one of the strong points for dbus/system since we'd not need to do authentication ourselves.
 
×
Reply to zbenjamin
Also not available in our minimal images: polkit, this would've been one of the strong points for dbus/system since we'd not need to do authentication ourselves.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  1 day ago by zbenjamin | Reply

  varlink seems to be the most promising one for now, so i will go with that

×
Edit Comment 11670
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
varlink seems to be the most promising one for now, so i will go with that
 
×
Reply to zbenjamin
varlink seems to be the most promising one for now, so i will go with that
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  about 8 hours ago by zbenjamin | Reply

  After some playing around with varlink it turns out that it has limitations when it comes to bidirectional communication. Messages must be strictly linear, one call -> direct answer. The server can not send spontaneous messages to the client without a previous message call. There is a way to stream "more" answers but it would require to have 2 sockets per client. Things like "prompt user" or "progress" would need a monitor socket making the whole architecture way too complex. We want to have a simple API clients can use

×
Edit Comment 11754
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
After some playing around with varlink it turns out that it has limitations when it comes to bidirectional communication. Messages must be strictly linear, one call -> direct answer. The server can not send spontaneous messages to the client without a previous message call. There is a way to stream "more" answers but it would require to have 2 sockets per client. Things like "prompt user" or "progress" would need a monitor socket making the whole architecture way too complex. We want to have a simple API clients can use
 
×
Reply to zbenjamin
After some playing around with varlink it turns out that it has limitations when it comes to bidirectional communication. Messages must be strictly linear, one call -> direct answer. The server can not send spontaneous messages to the client without a previous message call. There is a way to stream "more" answers but it would require to have 2 sockets per client. Things like "prompt user" or "progress" would need a monitor socket making the whole architecture way too complex. We want to have a simple API clients can use
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview