Jump to content
OpenSplice DDS Forum


  • Content count

  • Joined

  • Last visited

About guy.volckaert@meggitt.com

  • Rank

Profile Information

  • Company
    Meggitt Training Systems Quebec
  1. guy.volckaert@meggitt.com

    Mapping a partition to a channel

    Hi, I would like some help modifying my ospl.xml file to essentially associated a partition name with a specific channel. In essence, I need to add a new network channel (i.e. multicast address) to the ospl.xml file. This new channel would be dedicated for specific types of topics. I was planning to publish those specific topics via a unique partition name (for example: "session.group01"). When I publishing a topic using this partition name, it would be published through the new channel I added. Can someone provide an example ospl.xml that illustrates how to do that. I read the "OpenSplice_Deployment.pdf" document but I still don't know what needs to be done. BTW: I also attached the ospl.xml files that I'm currently using. Thanks, ospl.xml
  2. guy.volckaert@meggitt.com

    DataReader Bloating

    Just to let you know that I'm using boost v1.42.
  3. guy.volckaert@meggitt.com

    DataReader Bloating

    Hi, I noticed that SIMD seriously "bloats" the size of the application. I have a simple class that instantiated several dds::DataReader (approx. 20) where each data-reader is associated with a different topic. When I compile my class it generates an OBJ file that is > 350MB which takes forever to create! I decide to investigate why this is occuring and I found that the root cause is boost::signals2. In essence, each dds::DataReader instance creates 7 boost::signals2 instances stored in a boost::tuple<> - one for each event (like dds::on_data_available). See simd-cxx-v0.10\src\dds\peer\reader_impl.hpp. If I comment out all references to boost:signals2, then OBJ file drops to 7MB. That's 50 times smaller!!! That being said, I would strongly suggest replacing boost::signals2 by a custom callback implementation. Compiler: VS2005. Regards,
  4. guy.volckaert@meggitt.com

    How to get topic description

    HI, I was wondering if anyone knew how to get a description of a topic, programmatically. For example, when ever a topic is received I would like to print its content into a file (for debugging). I believe that the description of every topic in publish to insure consistent behavior for data readers/writers (maybe in XML format). I know that the performance tuner works in this fashion - and I would like to do the same in my code.