[omniORB] AMI

[Kevin Wooten]

I see an ami directory in cvs named in src/lib/omniORB/omniidl_be/cxx.
Although it seems the python files were for 3.1. I am inclined to add AMI
support to omniORB if someone else is not already on it?

 

Duncan, any suggestions for starting points I have looked through the spec.
and through the files in the AMI directory. For polling, I believe I am
going to be creating the IOP_C as usual and stuffing it into an associated
AMI_*_Poller and also a queue, some other thread will be feeding off of the
queue sending the requests. Maybe in certain cases the extra thread is not
needed? The poller's is_ready will be testing the state of the IOP_C to be
determining readiness. Sound ok? I have not though about callbacks much, or
when a poller's handler member is assigned to. Although it seems the IOP_C
may have to have knowledge of the callback since it needs to call it on
completion, but since the callback handler is a normal object, threading
issues seem to be passed on to the user.

 

Does it sound like I am in the ballpark?

 

Thanks,

Kevin Wooten

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20031117/549f2b90/attachment-0001.htm