i am doing a project at motorola. i have to clone the client side mobile phone software update engine.what is better suited for an embedded environment......threads or forks:
Threads require support libraries, so extra space is required in flash memory.
Updation of libraries may also be required so this may increase the installation time.
Though threads share resources, in our case the sharing is not substantial.
Forks may have increased RAM requirement but it depends upon number of forks . Each fork has its own copy of all the segments of the update engine.
Can anyone provide me with a comparison of advantages and disadvantages of threads and forks for embedded environment.