Hello @gbiggs,
[quote="gbiggs, post:16, topic:2619"]
While this is true, the other submission has managed to define an object model as well, and in addition kept it close to the existing DDS one.
[/quote]
And you see this as a positive aspect? Our model is simpler and more user friendly. For instance, how many people can digest DDS partitions? That said, we have a well defined mapping between XRCE resources and DDS topics.
[quote="gbiggs, post:16, topic:2619"]
Since the submissions have not gone to the AB yet, as far as I know, then there should not be any official AB reviews, which suggests to me that RTI asked for unofficial reviews from AB members. This may be why they are not public?
[/quote]
Are you an OMG member? If so I'll forward you the reviews. Both submissions went to the AB and the reviews were posted both on
ab@omg.org and
mars@omg.org. If you have access to those mailing list you'll be able to see them. I also recommend you take a look at those.
[quote="gbiggs, post:16, topic:2619"]
I didnt catch that even once during the presentation. Next time, put such an important motivating factor in your slides. :wink: RTI and co were much better at motivating their design decisions, and that put a positive spin on their submission.
You probably also should have put that requirement in the RFP, if its that important. The other submission cannot aim for a requirement they are not aware of.
[/quote]
It was impossible as the other vendors did not want to agree on such a low bound. The 24 bytes was the least we could agree on. This is why there is an evaluation on wire-efficiency. This matters were discussed at length, but again I don't think you attended those meetings, thus you are missing part of the history and the context. In any case, all of those documents are on the OMG archives, thus if of interest you to reconstruct it. Just search for presentation I did on XRCE for almost a year. starting from 2015!
[quote="gbiggs, post:16, topic:2619"]
That may have been RTIs reason, but the reason the rest of us present voted no is because we still have two vastly different submissions with no apparent readiness to work towards a single one. PrismTech even behaved in their presentation as if they are expecting RTI, Twin Oaks and eProsima to through away their submission and go with PrismTechs.
[/quote]
Yes, that is correct as it is since the very beginning that we are trying to do a joint submission. They've refused with futile arguments -- if you ask me. We have put lots of effort to trying to join but that has not been corresponded. A pity that you were not in the Bruxelles meeting, otherwise you would have had a taste of it.
[quote="gbiggs, post:16, topic:2619"]
Neither of these are required by the RFP. The RFP heavily directs the submitter towards the style of architecture that RTI/Twin Oaks/eProsima provided.
[/quote]
Again, you did not attend the end-less arguments we had during the RFP drafting. RTI does not want peer-to-peer in XRCE because they fear it could become as substitute for DDSI-RTPS. Again, this is not something I am inferring, but something that was openly debated during the RFP drafting. We don't have any issue with that as we think that having a more efficient protocol than DDSI-RTPS for some use cases would be extremely useful.
[quote="gbiggs, post:16, topic:2619"]
Yes, this is something that I was disappointed about. Hearing RTIs presentation talk about TCP/IP only seemed to rule out using it on things like Zigbee. But on the other hand, perhaps its readily adaptable?
[/quote]
For me that disqualifies completely the submission as in LowPAN environments nobody can afford to use TCP/IP...
[quote="gbiggs, post:16, topic:2619"]
It was very useful. I wish I had had this information during the presentation. I still have not had time to read the submissions in detail and unfortunately will not be able to do so before November, but fortunately we now have until February next year to try and resolve this situation.
And, as @vmayoral said, having code available would make a difference to how well we can judge things like implementation complexity. :wink:
[/quote]
I am glad that this helped clarifying the situation, please don't hesitate to ask any other question. Concerning the code availability we are working on that. I'll keep you posted.
A+
---
[Visit Topic](
https://discourse.ros.org/t/ipc-in-ros2/2619/17) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)