Quote from: sottwell at Jan 30, 2007, 09:00 AM
the ability to produce and consume stateful messages into specific containers across requests
This produced one of those "Huh?" moments, like 20 years ago when I had a Dos machine with no hard drive and two 5-1/2" floppy drives, and the first program I bought told me to "insert data disk in drive B". Hopefully this will come to be as understandable in time
Just think of more flexible $_SESSION variables, which get persisted across requests (i.e. they are stateful). Configure error logging from the manager in container A, use container B as a stack of error messages from context B (a web application) that are presented and available to the user in that context only, or use yet another container to store progress for an AJAX installation process. These kinds of "state machines", which are isolated from each other, can be manipulated as any array can be, are stored to disk, memory, a database table, or wherever you decide, and can be used for just about anything that needs to store or access stateful data. Unlike $_SESSIONS though, they can be ignored and avoided unless specifically needed. On Demand State Machines? Does that sound any better? Nah! LOL
Anyway, I hope that makes it sound a little more like something useful and less like your analogy above...though as with anything, there has to be a discovery process which (hopefully) leads you to understand where to actually insert the disk.