> 11.04.2011 14:59, Vlad Khorsun wrote:
>>> It just don't have enough advantages over old ISC API.
>>
>> With this new API many simple programs (like yours, for example) will
>> be easy to write and require
>> NO additional access layers.
>
> Not quite so. "Easy to write" (for me) means "use well documented API which
> has enough
> examples of usage". Nothig from this is applied to the new API.
Do you have completed API somewhere ? Where do you read that API is already
completed and
documented ? This mailing list is for developers of Firebird, and we talk about
work in progress here.
All you can look at - is the source code, so far. It will be documented at
appropriate time of course.
You can ask even now about its intended usage, if it is not obvious to you, but
don't expect wide
examples.
> And, BTW, what "additional access layers" you have on mind? Y-valve?
I speak about "drivers", such as IBPP, IBX\FIB+, ODBC, etc
>> New features (do you need longer SQL identifiers ?) also will be implemented
>> in new API.
>
> They can be implemented in an old API as well.
So far i know no plans to extend XSQLDA.
>> Call overhead also will be less than with ISC API.
>
> How big performance gain do you expect from it?
I don't know. When it will be ready, you are welcome to test it.
> AFAIK, CPU time wasted in old API
> serialization is microscopic in comparison with network or disk interaction
> time.
Its not about serialization. Its about converting of data between formats
and calls thru many
levels of internal functions.
Regards,
Vlad
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
