[omniORB] AMI

[Jochen Behrens]

Hi all,

I'm just wondering if omniORB will support AMI in the near future.
Is someone currently working on this issue?

Thanks,
Jochen

[Duncan Grisby]

Post by Jochen Behrens
I'm just wondering if omniORB will support AMI in the near future.
Is someone currently working on this issue?

Nobody is currently working on it, as far as I am aware. I have done
some thinking about how to best implement it, but haven't done any
development work yet. Are you volunteering? :-)

Cheers,

Duncan.

[Jochen Behrens]

Hi Duncan,

In general, I'm indeed inclined implementing some AMI stuff. It would be
a good opportunity to give back some benefits to the community. I'm
using omniORB for years in different projects, and in my opinion omniORB
is up to this day a very good leightweight alternativ to the TAO ORB.
For the moment, I'm emulating AMI on application level as a workaround.
That works fine, but providing it on ORB level would be much better.

However, I'm not really sure if it is feasable (with respect to time) to
volunteer. But I will have a discussion with my employer. Whether I can
spare time for omniORB development would mainly depend on the effort
estimations.

You mentionend that you already have some implementation ideas. Do you
think about the callback or polling model (or even both)? Personally, I
would prefer the callback approach.

Apart from any decisions I will have a look into the sources asap.

Best Regards,
Jochen

Post by Duncan Grisby

Post by Jochen Behrens
I'm just wondering if omniORB will support AMI in the near future.
Is someone currently working on this issue?

Nobody is currently working on it, as far as I am aware. I have done
some thinking about how to best implement it, but haven't done any
development work yet. Are you volunteering? :-)
Cheers,
Duncan.

[Duncan Grisby]

On Wednesday 10 January, Jochen Behrens wrote:

[...]

Post by Jochen Behrens
However, I'm not really sure if it is feasable (with respect to time)
to volunteer. But I will have a discussion with my employer. Whether I
can spare time for omniORB development would mainly depend on the
effort estimations.
You mentionend that you already have some implementation ideas. Do
you think about the callback or polling model (or even both)?
Personally, I would prefer the callback approach.

What do you mean about callback or polling model? You mean the
application-level view of AMI? To be a proper AMI implementation, it
has to support both.

The main challenge in implementing AMI, and the bit I've been
contemplating, is to modify the omniORB connection management code so
that it's possible to start a call on a connection, then carry on
without blocking waiting for a reply. That requires changing some of the
fundamental assumptions in the connection management code. It's somewhat
tricky to extend it, not least because it's a very performance critical
bit of the code.

I can point you at the relevant bits of the code if you're interested in
having a look at it.

Cheers,

Duncan.