[mico-devel] Is MICO's Event Service FIFO?

Hi, I am wondering if MICO's Event Service is delivering events in FIFO order. E.g. there is a supplied event A that _causes_ consumer #1 to supply an event B on the same channel (i.e. A triggers B). Is it possible that another consumer #2 receives B _before_ A? How does the

Re: [mico-devel] event service method push hangs

service dispatcher and threading model. Do you have also linux setup where you will be able to perform the same test? It might be interesting to know if it is win32 specific or general issue... Please keep us posted! Karel On Thu, 26 Oct 2006, Patrick Gräbel wrote: Hi! I implemented

Re: [mico-devel] Different treatment for localhost communication?

to use them and also try to use this demo in order to get an idea about the communication speedup. Karel On Thu, 28 Sep 2006, Patrick Gräbel wrote: Hi, I guess, the actual data transfer of CORBA is implementation specific. If that's true: is MICO using sockets for client/server

Re: [mico-devel] Building mico on Cygwin

Hi! I experienced the same linking problem, but I solved it by adding the lib crypto (and maybe ssl) somewhere in the Makefile. Search for gcc's -l parameter inside the Makefile (maybe more than a single one). Seems that libssl depends on libcrypto which does not get linked via the make

[mico-devel] Different treatment for localhost communication?

Hi, I guess, the actual data transfer of CORBA is implementation specific. If that's true: is MICO using sockets for client/server communication on localhost, too? Does MICO use a more efficient way or just a different technique (e. g. shared memory) for this special case? Thanks -Patrick

[mico-devel] Make fails on Cygwin (idl tool aborts)

Hi! The Cygwin make process produces an error (MICO 2.3.12rc1): the idl tool aborts with an assertion message. I am using the most recent gcc 3.4.4 for Cygwin. Any idea what caused this crash or how to solve this issue? I did not succeed in compiling MICO on Cygwin for weeks now, but it seems