Taral wrote:
> mico 2.2.6 has sufficient services support for CORBA to proceed.
I know some people thinks mico is great but I have some concerns:
* I can't even get it to compile on my workstation at work, upgraded both g++ to egcs and libg++/libstd++. Still it
doesnot compile cleanly, and it is easy to track the problems in C++ (not my favoite) and strange #ifdefs. I think I
havegot some working version at home, will check.
* BIG! "make -k" takes forever.
* Compiling the output stubs of MICO require a machine with at least
64MB RAM (hearsay).
* requires C++ (and very specific versions too). This a new requirement for compiling PgSQL. (what state are the
C-bindingsin theses days?)
I am afraid that all this is going to put and end to the happy
"fetch src and compile on any favorite old platform" way of life
in the PgSQL-community.
As long as these points are not resolved I think Tom L. will have to
continue fixing the old FE/BE-protocol, since CORBA will have to be
(very) optional on most platforms.
>[...]
> what I have now is not pretty). If anyone else wants to
> work with me on this, it might get done sooner. Otherwise, my research
> project takes precedence.
Why not put what you have in the CVS? The files in src/corba is pretty
old.
I have planned to get into this because did some coding around the
FE/BE-protocol and would love to see a clean object-based communication
in PgSQL instead the current one. Let us see what you have got and what
is
still missing in more lightweight alternatives to MICO.
best regards,
Göran.
