You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current SOME/IP specification did not take into consideration the uPClient library concept and ideas in that the translation to/from uMessages to SOME/IP messages will be done inside of the up-client-someip-xxx library under uTransport implementation. the spec requires some cleanup and clarification to align with latest architecture and concepts.
The text was updated successfully, but these errors were encountered:
The following change is a reboot of the SOME/IP specifications in an attempt to drastically simplify to show how we map up-l1 messages to SOME/IP messages and uSubscription messages to SOME/IP-SD messages. the older specifications had a lot of uProtocol version 1.3.6 concepts (cloudevents) that were rather complicating the situation.
#93
The current SOME/IP specification did not take into consideration the uPClient library concept and ideas in that the translation to/from uMessages to SOME/IP messages will be done inside of the up-client-someip-xxx library under uTransport implementation. the spec requires some cleanup and clarification to align with latest architecture and concepts.
The text was updated successfully, but these errors were encountered: