Corba has two major flaws: complexity and performance. The Cute server enables developers to use what they already know (Qt's signals and slots) to communicate

Corba has two major flaws: complexity and performance. The Cute server enables developers to use what they already know (Qt's signals and slots) to communicate over a network transparently. Clients interact with remote signals and slots as if they were local. The signals and slots mechanism provided by Qt fits perfectly as a communication protocol. For example, no polling is necessary on the client-side with remote signals. Also, the Cute server uses epoll-based event dispatchers (with Qt, custom event dispatchers inherit the QAbstractEventDispatcher class) to provide high-performance network data processing while supporting the signals and slots mechanism. With the Cute server and Cute client SDKs, instead of creating/parsing messages and interacting with a server/clients, developers only have to write QObject-derived classes and establish remote signal-slot connections or call remote slots directly to communicate over a network.