Releases: COVESA/vsomeip
Releases · COVESA/vsomeip
2.5.1
- Removed payload size limit. By default messages with an arbitrary length can
now be sent locally and via TCP. The payload-sizes configuration file array is
now used to limit the payload size for the specified endpoints instead of
increasing it. There are two new configuration file parameters:- max-payload-size-local: limit maximum allowed payload size for node internal
communication. - buffer-shrink-threshold: variable to control buffer memory deallocation
after big messages have been processed. For more information see the
vsomeipUserGuide.
- max-payload-size-local: limit maximum allowed payload size for node internal
- Fixed cleanup of endpoints for subscriptions using an exclusive proxy
(selective) which unnecessarily increased the number of open file descriptors. - Fixed assignment of predefined application IDs via autoconfiguration.
- Decouple start of routing manager from network availability.
- Made number of internal threads per application configurable.
- Postpone notify_one events sent from subscription handler to ensure correct
message order on receiver side.
2.5.0
- Added notify-/notify_one-methods to enable flush control for notifications.
- Restructured configuration to be a separate module (preparation to enable
the usage of compiled configurations to speed-up startup) - Added vSomeIP-Security: Socket authentication based on Linux-credentials
together with further security checks using configurable policies. - Fixed pending subscriptions had not sent out if subscribing application
hosts the routing manager. - Fixed crash in vsomeipd due to concurrent access when closing/shutdown socket.
- The service discovery now debounces newly offered service instances to avoid
sending out the offers of the same service instance with a too high frequency.
The default debounce time is set to 500ms. It can be changed via the new json
file parameter service-discovery/offer_debounce_time.
2.4.3
- Fix receiving of UDP frames containing multiple SOME/IP messages via UDP from
external service instances