I’ve finally released the next stable version of omniEvents. This incorporates the huge number of bugfixes. Thanks mostly to Dirk Siebnich’s relentless testing, I’m confident that this version of omniEvents is by far the most stable and robust yet. Read the rest of this entry »
GCC is quite pedantic, so code like this can cause problems:
CORBA::String_var s = ... s[0] += 1;Read the rest of this entry »
Normally a CORBA application processes each request in its own thread. So the author of a CORBA servant must always be aware that their methods may be running concurrently in multiple threads. Critical sections must be identified and locked accordingly.
Multi-threaded programming can be quite a pain, and all that locking, unlocking and context-switching can be a drag on performance. The SINGLE_THREAD_MODEL seems to offer a way to escape all these worries. Sadly it doesn’t deliver on that promise. Read the rest of this entry »
CORBA does not have the concept of distinct client and server applications. An application may both make and receive CORBA method calls. When it makes CORBA method calls it is behaving as a ‘client’. When it receives CORBA method calls it is behaving as a ’server’. Read the rest of this entry »
