At 01:09 AM 11/22/2001 -0500, Uri Guttman wrote: >>>>>> "SA" == Stephen Adkins <[EMAIL PROTECTED]> writes: >how does a message get delivered asynchronously? i see only calls such >as > > # receive next message from sender > $message = $messaging->receive( > sender => "stephen.adkins\@officevision.com", > ); > > # receive message associated with ticket > $message = $messaging->receive( > ticket => "XP305-3jks37sl.f299d", > >this implies that a component would either block or have to poll to get >messages. or will a callback be made and then this call has to be made? >if so, what is the callback method name and how is it set? this may be >too much to ask for now, but seeing the above code triggers my brane.
Hi, The Context object is the guardian of the event loop. If it receives notification of the arrival of a message associated with a ticket, it can go receive that message. Therefore, there may need to be a P5EEx::Blue::Context::Stem if Stem usually controls the event loop. Contexts which do not support true asynchronous notification may emulate it by polling. By the way, those were all quick API's, the purpose of which is to get us going in a direction. Obviously, the API's would need to be fleshed out. However, one of the goals of being able to rely on a standard Config Component is that only the things which an application *really* needs to control should be exposed through the API. The rest of the details should be controlled under the API by the application deployer (author of the configuration). Stephen
