elBoberido on master
iox-#27 Add new queue policies … iox-#27 Add options client port… iox-#27 Use client options in c… and 13 more (compare)
getServiceRegistryChangeCounter()then. Could you have a look at the issue and post a comment with your thoughts on it? Thanks!
std::optionalare custom implemented in C++14 and widely used in iceoryx.
RPCBaseHeaderusage for Request / Response communication. Thing is that,
ChunkSenderAllocates a chunk with
ChunkHeader. Hence we cannot use
ChunkSenderfor now to allocate request / response chunks. We also discussed regarding using
ChunkHeader. But my question was, shall we treat RPC header as User headers? as its implementation is not going to be upto the user. Or is it better we create a base header class for both types of headers?
posixCall. Besides the name change, the abstraction now uses the Builder Pattern and makes it easier to use. The second PR will almost definitely affect you since the
iceoryx_utilsgot renamed to
iceoryx_hoofs. The idea behind this change is to make this building blocks more prominent and make them visible as standalone library which could also be used without
iceoryx_posh. The renaming has a rather big effect on your local branches. Please take care that new files you created in
iceoryx_utilswill also be moved to
iceoryx_hoofswhen you merge/rebase with master.
iceoryx_hoofs. Interesting name if I may add. Is that the name for the oryx hoof? or another 'abbreviation' (https://www.abbreviations.com/HOOF)?
@yeswalrus Currently, there is only one running instance of RouDi per system allowed, you can check it by trying to start another instance of RouDi that will fail with an error message.
The recommendation is to run RouDi in multiple docker containers optionally orchestrated by
docker-compose to test networking. An example how this can be done is here.
The current dds gateway example on master is unfortunately broken but there is a bugfix in the pipeline on this branch if you want to try it.
initRuntimewith a second parameter for the RouDi IPC name. On the RouDi side this could also be done either by environment variable or by a setting in the config file. One thing I don't have a solution for is when you want an application to use multiple RouDi to transfer data between domains but maybe that's a task for DDS.