[omniORB] Implementation Repository

[Thomas Lockhart]

OK, I've gotten the tarball from the mailing list posting (but would be 
happy to post it also so folks don't have to figure out how to peel it 
out of the text message).

I notice that the sources are labeled as ".c++" rather than the ".cc" as 
used in omniORB and as commonly used in other packages. Would you be 
opposed to having these files relabeled with that convention?

I'm not sure if there was a decision on whether this is a standalone 
package or something inside the omniORB tree (and later the omniORBpy 
tree too). If it is standalone, I can work on autoconf support, which 
should be pretty easy with enough borrowing from the omniORB 
infrastructure. If it is merged, then most of the make system can just 
be adopted from an existing example.

I'm curious to see what it will take to get server-side python support.

                    - Tom