someip communication middleware bindings impl - #1036
sergejwinterbmw wants to merge 2 commits into
Conversation
Issue: SWP-279538
Issue: SWP-279538
a9fd0f1 to
4fee53a
Compare
| } // namespace detail | ||
|
|
||
| template <typename SkeletonServiceElementBinding, typename SkeletonServiceElement, ServiceElementType element_type> | ||
| //TODO: can this be changed to not change all callsite for every added binding? |
There was a problem hiding this comment.
Ie:
template <typename SampleType>
SampleType SampleTypeOf(const SkeletonEventBinding<SampleType>&);
and then in someip lambda
using SampleType = decltype(detail::SampleTypeOf(std::declval<const SkeletonServiceElementBinding&>()));
At the end You need SampleType or ?
|
|
| /// Holds everything that differs between two instances of the same service interface. In contrast to the LoLa binding | ||
| /// there are no shared memory sizes or slot counts here, since SOME/IP transports serialized messages over a socket | ||
| /// instead of shared memory. | ||
| class SomeIpServiceInstanceDeployment |
There was a problem hiding this comment.
This deployment would need more params in practice that can even be SOME/IP stack-dependent.
The question is if we will provide those as Key/Value, untyped or no support at all. Some kind of support would allow no need to patch upstream shared code in which we are now
|
Additionally, there is less of a funny effect that happens. If ie example will create Event for std::array, the code will instantiate both SomeIP and Lola implementations and I guess the linker cannot remove them since it has no clue what exactly will be used. Just noting this, may be helpfull for code size investigations. |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If this PR is still relevant, please leave a comment or push new changes to keep it open. |
No description provided.