Comments on: EMI Blog Background http://www.embeddedmarketintelligence.com Embedded Topics and Best Practices Mon, 06 Sep 2010 02:12:06 -0600 http://wordpress.org/?v=2.8.5 hourly 1 By: Berbatov http://www.embeddedmarketintelligence.com/about/comment-page-1/#comment-814 Berbatov Mon, 19 Jul 2010 02:48:51 +0000 http://www.embeddedmarketintelligence.com/?page_id=2#comment-814 Hey , you have a really nice blog , I'm going to put a link to it on my site, so I will send you some quality traffic :) Cheers! Hey , you have a really nice blog , I’m going to put a link to it on my site, so I will send you some quality traffic :) Cheers!

]]> By: Clark Tucker http://www.embeddedmarketintelligence.com/about/comment-page-1/#comment-10 Clark Tucker Fri, 18 Dec 2009 01:50:50 +0000 http://www.embeddedmarketintelligence.com/?page_id=2#comment-10 Jerry, I just read your article "Making the case for commercial communication integration middleware" on embedded.com with interest. As a communications middleware vendor in the embedded market, I was of course intrigued. You mention RTI as a vendor of embedded middleware. I wonder if you are familiar with our CoreDX DDS product? It is an implementation of DDS, interoperable with RTI's DDS product, compatible with the OMG DDS standard (API and wire-protocol), extensive Quality of Service support, and with a significantly smaller footprint than RTI's product. (For comparison, a typical application linked with CoreDX DDS is 250KBytes vs 4+MBytes.) If you are interested, we would be happy to discuss our product in more detail. And, if you find yourself writing another article on embedded communications middleware, we would love to contribute or participate! Thanks! --Clark Tucker President/CEO Twin Oaks Computing, Inc Jerry,

I just read your article “Making the case for commercial communication integration middleware” on embedded.com with interest. As a communications middleware vendor in the embedded market, I was of course intrigued. You mention RTI as a vendor of embedded middleware. I wonder if you are familiar with our CoreDX DDS product? It is an implementation of DDS, interoperable with RTI’s DDS product, compatible with the OMG DDS standard (API and wire-protocol), extensive Quality of Service support, and with a significantly smaller footprint than RTI’s product. (For comparison, a typical application linked with CoreDX DDS is 250KBytes vs 4+MBytes.)

If you are interested, we would be happy to discuss our product in more detail. And, if you find yourself writing another article on embedded communications middleware, we would love to contribute or participate!

Thanks!
–Clark Tucker
President/CEO
Twin Oaks Computing, Inc

]]>