Hi,

FreeTDS (note, I am the original author of FreeTDS) implements the
APIs used by either Sybase or Microsoft which means dblib, ctlib, and
ODBC. ctlib has support for asynchronous communications but does not
expose the socket file descriptor to the rest of the world, but since
it's open source that could be made to happen, it's just not in the
API presently.

I'm interested in your thinking on using pthreads to work around the
blocking API, I've been using a coprocess communicating over unix
domain sockets to do the same thing (pending conversion to
non-blocking module of course).

Server-side javascript is one idea, the V8 stuff looks very
interesting. The primary use was for intranet users where the
database credentials were supplied by users, so the credentials
problem was not an issue in that context.

Brian

2010/7/31 agentzh <agentzh@gmail.com>:
> On Fri, Jul 23, 2010 at 6:18 AM, Piotr Sikora <piotr.sikora@frickle.com> wrote:
>> It's great that you're also supporting MS SQL Server (via FreeTDS),
>
> Hmm, it'll be interesting to implement an ngx_freetds or ngx_sqlserver
> module using FreeTDS and the infrastructure used by both ngx_drizzle
> and ngx_postgres. I myself don't know how well the non-blocking
> support of FreeTDS is. Hopefully it does not suck as Oracle's OCI, or
> we'll have to use internal pthreads to work around those APIs that
> cannot be made non-blocking :)
>
> And as others have already pointed out, I'm scared to see db passwords
> and raw SQL query strings appear in JavaScript code on DB Relay's home
> page. Hopefully that piece of JS is intended to run on server side
> only (via the ngx_js module or V8 or something else) ;)
>
> Cheers,
> -agentzh
>
> P.S. I'm one of the authors of ngx_drizzle and ngx_postgres :)
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx