i started looking at corba again yesterday, got this idea that maybe it would be a wise idea not to reinvent the wheel again and at least check it out… anyway, i´ve been using a dead-simple c/c++ interface for extending my tiny 3d project, but when you start to think about when an existing interface is updated to v2 (keep both v1 and v2 for backwards compatibility?), or there is a v1.0, v1.1, v2.0.3 of an extension dll, which one to load? which one does the scene file you´re loading, dating back 2 years back, expect? so i´ve basically slipped into corba/com territory, and got some thoughts before rewriting the core again 
my user interface right now is confined to one single window, everything is cooperating happily, everyone is drawing their own opengl stuff… but what if i bridge everything with corba? that means one module could be running on my other computer (which could be cool? :)) , but would i have to keep opengl drawing to the application process space? i thought about passing along window handles to get the opengl context, but i have no damn idea if it would work. my other concern is that i´d make everything a black box, so every data object is manipulated indirectly, by reference… quite contrary to what i´ve been making so far, i´ve passed data directly between operators. having a heavy data stream between corba objects somehow sounds like a bad idea, i was thinking about something like a compositor, sending HD frames over LAN between operators? BAD IDEA!
any thoughts or help would be appreciated!
jens.