Context Navigation

Changes between Initial Version and Version 1 of Ticket #230, comment 25

initial	v1
6	6	4. The consumer thread starts a second worker to process the second request.
7	7	5. The second worker finds out that the instance is not yet created (since the first worker hasn't completed its job yet) and enters this awful while loop.
8		6. The first worker goes on with instance creation and comes to a point it creates a new thread whose only role is to create an object of the `WEmbedded~~Winfow~~` class and then starts to indefinitely wait on this thread's completion.
	8	6. The first worker goes on with instance creation and comes to a point it creates a new thread whose only role is to create an object of the `WEmbeddedFrame` class and then starts to indefinitely wait on this thread's completion.
9	9	7. However, because the second worker is spinning like hell in a while loop, the new thread does never get a chance to start its execution.
10	10	8. As a result, the instance is never created, the state is never changed to what the second worker expects.