using the carob API Was: latest stable combination?

On 6/5/07, Marc Herbert <Marc.Herbert-NAAfj4rwCWC8rjiVs5Nzzw@xxxxxxxxxxxxxxxx> 
wrote:
> "Gabor Szokoli" <szocske-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> writes:
>
> > Could someone here recommend a stable combination of sequoia, carob
> > and odbsequoia to use? I have found reference to 2.8.2, 0.5.2 and
> > 0.5.2a respectively.
>
> You can use the latest release of every component except for
> odbsequoia, where you must checkout the latest code from CVS.
>
> odbsequoia is at this stage just a working prototype. Check its
> documentation for more details.

Thank you for your kind answer.

Meanwhile we have realised odbsequoia lacks some features vital to us
(setting attributes and options like timeouts) and adding support
would take longer and be still less satisfactory than using the the
carob C++ API directly.

So here's some feedback on using it for the first time:

- #defines on common words like "begin" or "close" pollute the global
"namespace". Point being, #defines are not confined in C++
namespaces, please consider using ENUMS or const statics instead in
the future, which are.

- Proper carob operation requires a UTF-8 locale, as I am sure it is
docuumented somewhere. Still, the failure mode for the lack of one
could be a bit more graceful: we see empty strings sent over the
network, but the login credentials are substituted back in the error
messages, as if they have been transmitted.

Other than these inconveniences, it looks like a great product, thanks
for the effort!


Gabor Szokoli
Deverto Systems