This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
laforge gerrit-no-reply at lists.osmocom.orglaforge has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-hnodeb/+/26357 ) Change subject: Initial implementation of LowerLayer UD Socket ...................................................................... Patch Set 6: I'm not sure if it made sense to alrady "factor out" some of the core/generic osmo_prim-socket related handling and make osmo-hnodeb directly start with just being a user. I'm thinking roughly of the level of abstraction that libosmo-netif provides for creating a server and client around a SEQ_PACKET unix domain socket, and making the related send/receive functions already aware there is something with a primitive header passed around. In fact, the user API could directly work with osmo_prim as we know it, hiding the serialization/deserialization inside the API. Yes, it's easier doing it "flat" here in the application, but I'm afraid if we postpone the "generic socket" part for too long there will be ugly fall-out later when migrating due to some subtle difference here or there. -- To view, visit https://gerrit.osmocom.org/c/osmo-hnodeb/+/26357 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-hnodeb Gerrit-Branch: master Gerrit-Change-Id: Icaabb2206d6f141d4fba47dedf71f8ec37e6257d Gerrit-Change-Number: 26357 Gerrit-PatchSet: 6 Gerrit-Owner: pespin <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Comment-Date: Tue, 30 Nov 2021 07:49:57 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20211130/8219c8a4/attachment.htm>