-
Notifications
You must be signed in to change notification settings - Fork 77
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
How server get client's connect by CommonApi? #30
Comments
kheaactua
pushed a commit
to kheaactua/capicxx-core-runtime
that referenced
this issue
Nov 12, 2023
* capicxx-someip-runtime 3.2.3-r8 - Changed level logs from warning to info when address_aliasing is activated - Fix incorrect timings in logs - vSomeIP Security: Update vsomeip_sec - Use steady_clock instead of high_resolution_clock - Extend SomeIP::ClientId interface to be more flexible when creating instances - Outputstream: Fix endianness issues when writing array lengths - Linux: avoid static initialization of std::mutex. - Changed the default width of a serialized enumeration from "backing type width" to 1 byte. - Updated the subscriptionMutex_ to a recursive_mutex. - Added OSS information for RSE. - Fixed open source compliance issues. - Ensure cleanup- and detach-thread do not attempt to join themself. - Removed GENIVI copyright line - Extended error message on event deserialization error. - Implemented correct sending/receiving of boolean values. - Initialize lastProcessing_ time - Update android build files - Array of uint8_t: Check remaining bytes before calling vector::assign. - Add method to convert from capi client to someipclient. - Fix Address overwriting - Adapt to CommonAPI 3.2.2 - Added main loop supervisor * Fix Copyright field and github link in README file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
environment: vsomeip+CommonApi
As server, whether there is a interface or function to get client connected now by CommonApi?
And how to get the count of all clients connected to server?
thx!
The text was updated successfully, but these errors were encountered: