Subject | Re: [Firebird-Architect] RFC: External Engine API |
---|---|
Author | Geoff Worboys |
Post date | 2007-12-12T00:44:55Z |
Hi Roman,
[...]
any serious Java - it seems I still have much to learn. Not
sure that I want to learn that stuff anyway, it sounds nasty.
If we want a C++ friendly API then it seems much the same
should be usable even in Java without tricks.
exactly what is meant/implied by "External Engine API". Those
of us not fully engaged in the details of the Firebird engine
do not always understand the terms you are using (witness the
recent confusion over "TLS" that also bothered me for a while).
With an explanation of "External Engine API" we may be able to
generate more interest from library maintainers.
--
Geoff Worboys
Telesis Computing
[...]
> but there are really-really many "tricks" in Java[...]
> that you don't have in Delphi or C++.
> And these are more or less normal techniques in modern JavaThanks very much for your explanation. I've never gotten into
> - just check what in O/R mappers is used...
any serious Java - it seems I still have much to learn. Not
sure that I want to learn that stuff anyway, it sounds nasty.
If we want a C++ friendly API then it seems much the same
should be usable even in Java without tricks.
>> I think the thing would be toOne thing that may help is a more detailed explanation of
>> ask the library developers what they need/want - particularly
>> in the case of Delphi where (I assume most) development takes
>> place via an existing library rather than directly to the API.
> Oh yes... Unfortunately they are silent for some reason...
exactly what is meant/implied by "External Engine API". Those
of us not fully engaged in the details of the Firebird engine
do not always understand the terms you are using (witness the
recent confusion over "TLS" that also bothered me for a while).
With an explanation of "External Engine API" we may be able to
generate more interest from library maintainers.
--
Geoff Worboys
Telesis Computing