Sunday, October 24, 2004

From MSDN Library:
Monitor Synchronization Technology Sample -- This sample demonstrates how to use the Monitor class for thread synchronization. The Monitor type's static functions are used to enforce mutually exclusive access to a protected block of code.

Readme Location

For more information, see the Readme file at <SDK>v1.1\Samples\Technologies\Threading\MonitorSynchronization

Concepts Presented in This Sample

thread synchronization, samples; Monitor class, samples; AutoResetEvent class, samples; Interlocked class, samples; Threading namespace, samples; ThreadPool class, samples; WaitCallback class, samples; Thread class, samples; delegates, samples; ThreadStart delegate, samples; threads, samples; Delegate class, samples

Communicating Sequential Processes, or CSP, is a language for describing patterns of interaction. It is supported by an elegant, mathematical theory, a set of proof tools, and an extensive literature. The book Communicating Sequential Processes was first published in 1985 by Prentice Hall International (who have kindly released the copyright); it is an excellent introduction to the language, and also to the mathematical theory.
From this Wikipedia page: Communicating sequential processes

Friday, October 22, 2004

Working With Events Over Remoting by Russ Nemhauser: Subscribing to events of objects instantiated via remoting can be a tricky business. However, it is possible to build solid event publish/subscribe applications while using remoting simply by applying a few extra strategies then might not seem immediately obvious. Throughout the document, I will refer to the process that exposes the object for remoting as server and the process that instantiates an instance (local proxy) of a remote object as client. However, all of these processes may in deed take place on the same machine.
Murphy's Law calculator

.NET Remoting FAQ -- includes Changes for Remoting in .NET Framework 1.1 / Visual Studio 2003: Adjusting the typeFilterLevel to enable events, delegates and client-activated objects

Sunday, October 10, 2004

Learning Classifier Systems Software
Scientists Define Murphy's Law - things don't just go wrong, they do so at the most annoying moment.The formula, ((U+C+I) x (10-S))/20 x A x 1/(1-sin(F/10)), indicates that to beat Murphy's Law (a.k.a. Sod's Law) you need to change one of the parameter: U for urgency, C for complexity, I for importance, S for skill, F for frequency and A for aggravation.

Or in the researchers' own words: "If you haven't got the skill to do something important, leave it alone. If something is urgent or complex, find a simple way to do it. If something going wrong will particularly aggravate you, make certain you know how to do it."