Keruspe ( Marc-Antoine Perennou )

I have an application that listens on multiple ports. Currently I am implementing it using threads but I consider changing it to async. Can you provide an example on how I would implement multiple servers (listen on multiple ports and handle connections on each of those ports) using smol runtime?

Thank you

//Max

closed time in 10 hours

mhristache

created repositorycodepo8/full-card-click

Back to Basics: Creating a clickable card interface in plain HTML, CSS and JavaScript

created time in 11 hours

push eventsozu-proxy/sozu

Geoffroy Couprie

commit sha 1e2da00f86ea8c60481a69fc8e306096977c89be

move target_to_backend to sozu-command-lib

view details

push time in 13 hours

push eventsozu-proxy/sozu

Geoffroy Couprie

commit sha b93414db2a3a6d8433dc6813de36ad47d2802617

make timeout members private

view details

Geoffroy Couprie

commit sha c833431580caffd8a8311a6d3cb3a9d0dfc6b362

move timeouts from std::time to the time crate

view details

Geoffroy Couprie

commit sha 8db6951236565c9eac5b3cbd7832ddd073eb779b

reactivate worker logging

view details

Geoffroy Couprie

commit sha 4fa04672a11e000a70bd4fd81d6db8c15ffa8df0

no need to pass the front timeout value from the poll loop

view details

Geoffroy Couprie

commit sha 5e70563bac42ce669371188a0cb0840f6461367b

introduce the request_timeout option request_timeout is the maximum time allowed between a client connection is open, and the entire request headers are received. This will help in mitigating slow DoS attacks. Once the headers are received, we update the timeout duration to front_timeout

view details

push time in 14 hours

issue openedCleverCloud/biscuit

New atom type: Set

It could be interesting to have a Set atom type in the spec.

We recently merged the feature into biscuit-go (see: https://github.com/flynn/biscuit-go/commit/19073ab908515f0e05662bc4084477f55e4e82dd)

This allows to group several atoms under a single one, and have constraints allowing to check if all or none the set values are included in a given set:

# given the fact:
users(#ambient, ["alice", "bob", "eve"])

# doesn't match, since eve is not in the constrained list
*allow($username) <- users(#ambient, $usernames) @ $usernames in ["alice", "bob"]

# match, $usernames does not contains any of "admin" or "root"
*allow($username) <- users(#ambient, $usernames) @ $usernames not in ["admin", "root"]

The set does not restrict embedding different atom types (ie: [#a, "alice", 42]) but I don't see much usage of that yet. It doesn't seem to affect the constraint anyway.

wdyt ?

created time in 15 hours

issue commentCleverCloud/biscuit

Retrieving a block index

This sounds neat! I'll give it a try soon

daeMOn63

comment created time in 15 hours

push eventCleverCloud/demo-nodejs-postgres-rest

Clément Nivolle

commit sha f5743e9cda9ad93b581d80ba0585ff844a408fec

Update index.pug

view details

push time in 16 hours

startedTeslafly/OpenBMS

started time in 18 hours

issue commentbus1/dbus-broker

Service file is not named after the D-Bus name

Thanks for the thorough explanation!

This service file is part of jack. Changing the service name would likely break too many things.

However, it renaming the file should work. I'll mention this upstream.

Indeed, if it is part of a release, renaming the file is the correct approach. Feel free to put me on CC, if any input from upstream dbus-broker is needed.

In particular, because it does not allow the existence of multiple implementations that provide the same service. E.g.: many apps provide org.freedesktop.Notifications. If they had to include a dbus service file with the name org.freedesktop.Notifications.service, it would not be possible to install them onto the same system.

Isn't it somewhat conflicting with the idea behind DBus: that there can be exist implementations of one single service? (though only one can run at once).

I think you are conflating dbus-interfaces with dbus-names. The term org.freedesktop.Notifications most likely refers to an interface, which any dbus client can implement, even in parallel with others. Similar to interfaces in Java, or abstract classes in C++, or traits in Rust, etc.

In contrast, D-Bus Well-Known Names are ways to identify a peer on the bus, hence it must be unique. Names are used to route messages, and are thus more comparable to pointers or references in normal programming languages. They do not define what type of object they point to, they are merely named identifiers.

WhyNotHugo