Michael Powell
2013-02-15 12:11:37 UTC
Hello,
I am entering a project where we decided C++ was the way to go. C++/boost
core engine, devices to be I2C exposed over a distributed object
architecture (enter CORBA potentially), and so on, to enable distributed
development potentially off-device, as well as on-device in production.
I am no stranger to distributed object technology stacks, like COM-family,
web services including WCF, and even a little CORBA, but it has been
several years for CORBA, so need a little practical guidance, specially for
targeting cross-platforms.
Development would occur on a Windows-based system and target ArchLinux/ARM.
What are our options? We can build the ORB to run on either platform? Can
it be statically linked with the client/server? Better to dynamically link
and let it run as a service?
However if performance suffers and the advantages of getting out of the
middle tier protocol management business aren't there, like can we talk
client/server over different asynchronous TCP/IP ports, then we may end up
rolling our own infrastructure. Not my first choice, I'd rather focus on
speed to market, but this is what we need to know.
Other than that, I'm unafraid of the age of CORBA, it's been around for A
WHILE (can you believe the first specifications were out in 1991?), so I
expect implementations to be nearly as solid as their age would allow.
Thank you...
Regards,
Michael
I am entering a project where we decided C++ was the way to go. C++/boost
core engine, devices to be I2C exposed over a distributed object
architecture (enter CORBA potentially), and so on, to enable distributed
development potentially off-device, as well as on-device in production.
I am no stranger to distributed object technology stacks, like COM-family,
web services including WCF, and even a little CORBA, but it has been
several years for CORBA, so need a little practical guidance, specially for
targeting cross-platforms.
Development would occur on a Windows-based system and target ArchLinux/ARM.
What are our options? We can build the ORB to run on either platform? Can
it be statically linked with the client/server? Better to dynamically link
and let it run as a service?
However if performance suffers and the advantages of getting out of the
middle tier protocol management business aren't there, like can we talk
client/server over different asynchronous TCP/IP ports, then we may end up
rolling our own infrastructure. Not my first choice, I'd rather focus on
speed to market, but this is what we need to know.
Other than that, I'm unafraid of the age of CORBA, it's been around for A
WHILE (can you believe the first specifications were out in 1991?), so I
expect implementations to be nearly as solid as their age would allow.
Thank you...
Regards,
Michael