QUOTE(John Rouse @ Jul 6 2007, 09:23 PM)
The main benefit of naming queues is if you are obtaining a queue by name somewhere. If not ,then this has no benefit. Queue references don't need names.
QUOTE(John Rouse @ Jul 6 2007, 09:23 PM)
The whole idea is to have a memory location that is specific to the process (object) instance and only that instance. This way two or three process's can operate independently and each process can have a method for doing/updating and seperate (reentrant) methods for monitoring.
I'm not sure I follow. What OO framework are you using? OpenGoop, LVOOP? If you create a new instance of your object then doesn't each instance already have a place to store data?
QUOTE(John Rouse @ Jul 6 2007, 09:23 PM)
I understand the notifier but admittedly
the behavior of notifiers is something I seldom can think of a "use case" for in my programming.
Whats a really good use case for a Notifier (over a queue) anyway?
Notifiers are basically occurrences with data. usually used to "wake up" loops and at the same time pass data to them. With the release of dynamic events and event structures, they become less important however still useful sometimes.