One reason to implement a Squeak native database connection, i.e. a 
socket level interface as opposed to a FFI call to a C library, would be 
to enable multiple threads in the image to execute transactions 
concurrently. My understanding of the Squeak VM and FFI is that once a 
Squeak thread descends into a FFI call all other threads in the image 
will be blocked. This can be undesirable in an environment where the 
image is servicing multiple client requests, say over the web, that 
generate independent transactions on the database.

-ram

lex at cc.gatech.edu wrote:

> Kamil Kukura <kamk at volny.cz> wrote:
> 
>>When trying to attract web developers from environments such as PHP, ASP 
>>or JSP, I'm badly missing a thing to show as how Squeak deals with 
>>external databases. Perhaps best way to connect to any DB is to use ODBC 
>>which scares me as it relies on FFI 
>><http://minnow.cc.gatech.edu/squeak/2424>
> 
> 
> FFI seems the proper way to talk to ODBC, and ODBC seems like a direct
> way to get portable database access.
> 
> Is fear the only reason not to use FFI, or is there a technical problem
> as well? Have you tried it?  Maybe we just need to smooth the process of
> getting everything set up?
> 
> 
> -Lex