In object-oriented programming, the concept of an active object refers to objects that exist in their own thread of execution and have their own address space.Calls to active objects are inheretly asychronous(i.e non-blocking) hence active objects are a better way to implement multi-threading than using raw threads. This is because active objects tend to multi-task co-operatively within a thread also using active objects does not require sychronization as opposed to using raw threads where data shared by threads must be protected with access synchronization primitives such as mutexes or semaphores.

lol...

webdezzi: lol...

lmao

Thanks. I think they are also known as "Actors".

harryobas: In object-oriented programming, the concept of an active object refers to objects that exist in their own thread of execution and have their own address space.Calls to active objects are inheretly asychronous(i.e non-blocking) hence active objects are a better way to implement multi-threading than using raw threads. This is because active objects tend to multi-task co-operatively within a thread also using active objects does not require sychronization as opposed to using raw threads where data shared by threads must be protected with access synchronization primitives such as mutexes or semaphores.

**whistling away**