<br><font size=2 face="sans-serif">Well.. after my hellish experience with TAO... I'd stay away from it, *IF* my goal was just to get an ORB....</font>
<br>
<br><font size=2 face="sans-serif">Basically....</font>
<br><font size=2 face="sans-serif">- TAO has a *LOT* of 'stuff' which is quite useful in building any large system (assuming you get TAO before you start). It probably has a class for making coffee in the morning too :-)</font>
<br>
<br><font size=2 face="sans-serif">- We had some code I had developed approx 6-7 years ago, which I tried to port to TAO, but unfortunately the effort was way too much</font>
<br>
<br><font size=2 face="sans-serif">- We just needed a nice simple, clean ORB that could function with our legacy code... and omniORB was the perfect choice</font>
<br><font size=2 face="sans-serif"> - Small/Simple to use</font>
<br><font size=2 face="sans-serif"> - Fully functional from a CORBA perspective</font>
<br><font size=2 face="sans-serif"> - Doesn't impose it's own design/implementation model onto our software</font>
<br><font size=2 face="sans-serif"> - EASY to build, and didn't have to add a new drive for a build area (which we had to do for TAO)</font>
<br>
<br><font size=2 face="sans-serif">Renny Koshy</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Richard Neswold <neswold@fnal.gov></b></font>
<br><font size=1 face="sans-serif">Sent by: omniorb-list-bounces@omniorb-support.com</font>
<p><font size=1 face="sans-serif">07/01/2004 10:38 AM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: Thomas Lockhart <lockhart@fourpalms.org></font>
<br><font size=1 face="sans-serif"> cc: omniorb-list@omniorb-support.com</font>
<br><font size=1 face="sans-serif"> Subject: Re: [omniORB] Fwd: How to make an application which is both an omniorb client and TAO server</font></table>
<br>
<br>
<br><font size=2 face="Courier New">Thomas Lockhart wrote:<br>
<br>
>> I have a TAO 1.2.1 server which also has to act as a client of other servers.<br>
> <br>
> "Must use" both omniORB and TAO seems to be a rather arbitrary <br>
> requirement. Both ORBs have a reasonable feature set and both are <br>
> reliable. Both also work as clients and as servers. I've had great <br>
> success with both, but never a requirement to mix them together in a <br>
> single application. I do have a simple example app which can be compiled <br>
> against *either* omniORB or TAO, so I know the conventions for the two <br>
> ORBs are not that different.<br>
> <br>
> I'd stick with TAO for the server.<br>
<br>
Wow! The omniORB community let this comment slide for two days? :-)<br>
<br>
I'm curious why you'd prefer TAO for the server, instead of omniORB. <br>
(I've used omniORB and MICO to familiarize myself with CORBA and haven't <br>
yet tried TAO.)<br>
<br>
-- <br>
<br>
Rich Neswold<br>
<br>
Fermi National Accelerator Laboratory<br>
Accelerator Div/Controls Dept<br>
voice: (630) 840-3454<br>
fax: (630) 840-3093<br>
<br>
_______________________________________________<br>
omniORB-list mailing list<br>
omniORB-list@omniorb-support.com<br>
http://www.omniorb-support.com/mailman/listinfo/omniorb-list<br>
</font>
<br>
<br>