On 18-Apr-07, at 3:03 PM, Guillermo wrote:

> And is normal that this kind of instructions (like SQLSelect) to be
> called in literally hundred of methods and several times in each
> method, is a gargantuan task don't made this synchronous. I think that
> this is the usual behavior of all databases API (like JDBC, ODBC....).

Usually the underlying library that those API's are built on is  
synchronous.

So any plugin using those libraries would also be. In fact many used  
to freeze the app until they finished while waiting for results, etc.
Some have API's that permitted a developer to yield time to RB so  
other threads could proceed while waiting for results.

You can do this with a socket but it's more work and you have to take  
an asynchronous socket and make it behave like it's synchronous.

Ask Marc at Aliacta .... it can be done but it's a fair bit of work.


I've worked with a lot of databases and only once had to deal with an  
async API.
Sybase used to ship one for VMS and man was it a pain to get right.
Result sets just randomly arrived when queries finished. ick !
We almost never used them because of this.

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to