[ace-users] Structured Event of Notify Service,
Is it SYNC method call?
Douglas C. Schmidt
schmidt at dre.vanderbilt.edu
Mon Aug 13 09:23:57 CDT 2007
To ensure that we have proper version/platform/compiler information,
please make sure you fill out the appropriate problem report form
(PRF), which is in
in older versions of ACE+TAO. Make sure to include this information
when asking any questions about ACE+TAO since otherwise we have to
"guess" what version/platform/compiler/options you've using, which is
very error-prone and slows down our responsiveness. If you don't use
the PRF, therefore, it is less likely that someone from the core
ACE+TAO developer team will be able to answer your question.
Naturally, we encourage and appreciate other members of the ACE+TAO
user community who can respond to questions that they have the answers
> I found Structured Event of Notify will wait for each consumer
> finished their push_structured_event(), one by one.
Yes, that's the default "single threaded" event channel model.
> Is this condition right ? or, Are there other setting can let it
> become publish/subscript model ?
It already is a publish/subscribe model. I think your actually asking
"Are there other settings that can let it become an asynchonrous
publish/subscribe model," right? If so, please take a look at the
various options related to threading, such as "-ORBRunThreads
There's lots more information about this in Chapter 27 of the OCI TAO
Developer's guide, which you can purchase at
Dr. Douglas C. Schmidt Professor and Associate Chair
Electrical Engineering and Computer Science TEL: (615) 343-8197
Vanderbilt University WEB: www.dre.vanderbilt.edu/~schmidt
Nashville, TN 37203 NET: d.schmidt at vanderbilt.edu
More information about the Ace-users