[Pkg-ace-devel] Re: Bug #1854: Reactor Implementations

[Konstantinos Margaritis]

On =CE=A0=CE=B5=CE=BC 23 =CE=A3=CE=B5=CF=80 2004 20:54, Raphael Bossek wrot=
e:
> Hi all, some informations on
> http://deuce.doc.wustl.edu/bugzilla/show_bug.cgi?id=3D1854
>
> I'm now able to create libACE_TkReactor, libACE_QtReactor,
> libACE_FlReactor and libACE_XtReactor libraries. I could achieve
> this by modifing the MakeProjectCreator files.

That's very nice. We're in the process of producing up to date ACE+TAO=20
packages for Debian and it would be really cool to be able to have=20
this also.=20
It would be really convenient if you could provide with a patch=20
against the current debian package sources (available in the upload=20
queue right now, not yet part of unstable).

> But have had to realise that TAO uses its own reactor
> implementations:
> ACE_wrappers/TAO/tao/{xt_resource.cpp,qt_resource.cpp}

> This appears to be a problem for me. libTAO is prebuild with
> reactor usage depending on the configuration at build time ?
=2E..

> So I have to create additional libraries for xt_resource.cpp and
> qt_resource.cpp too. Let say I will call them libTAO_XtReactor and
> libTAO_QtReactor as their counterparts libACE_XtReactor and
> libACE_QtReactor. This would mean, one file per shared library. I
> know a little bit oversized.

While personally i don't use any of these reactors, i believe the=20
choice to offer all of them would be quite a valuable addition both=20
upstream and to all the package creators.
Of course it would require some changes on the part of the developers=20
esp. if they already use one of the reactors, but personally I would=20
be ok with this change, if it would mean smaller libraries and less=20
dependancies...

Konstantinos