darkwing said:
ORB = Object Request Broker
it allows processes on different machines, written in different languages and running on different platforms, to talk to each other (make calls, exchange information). the interface is written in a simple language called IDL (interface definition language), which is then compiled on the target machine, in the target language, into client and server stubs. those stubs are compiled and linked in.
the ORB itself is a running process that brokers the communication across machines and processes (clients and servers can run on the same machine, fwiw).
neat stuff. on project #1, i set up a CORBA service to provide project data to legacy projects in the firm, helping them make the leap from batchfile processing to, well, the 20th century
this was in addition to the plethora of CORBA services we implemented for our project.
(I'm a hard realtime embedded systems guy, not a server guy.)
like my first job. mostly C, but sometimes you just gotta program in assembly.
Interesting story about your server projects. When you talk about a trading app did you mean stocks?
i can't go into much detail, but basically yes, both projects were in the financial industry.
as a sidenote to #2, this was a project i joined about a year and a half after it had been going. i had to undo some design damage, and about a year later we had most of it in place, performance issues aside.
this was just as EJB was coming into being, so we brought in a vendor to demonstrate their stuff. another developer and myself spent less than two weeks, using EJB, to duplicate almost the entire server tier the team had spent 2 1/2 years coding. kind of a morale killer, actually. in the end, management decided not to go w/ EJB, with which i disagreed. i thought it was a great timesaver.