freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: Tolga Ceylan <tolga.ceylan AT gmail.com>
- To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
- Subject: Re: [freetds] freetds async usage
- Date: Mon, 10 Nov 2014 11:26:22 -0800
It's more of an open question, any approach/implementation is OK.
This could be via ct_poll() sort of approach or freetds could expose sockets
for the application to monitor via epoll/poll, etc.
I've got no strict requirements or any dependencies to any specific library.
In other words, I want to manage multiple connections in a single thread
where freetds API should not block.
On Mon, Nov 10, 2014 at 2:01 AM, Frediano Ziglio <freddy77 AT gmail.com> wrote:
> 2014-11-07 21:50 GMT+00:00 Tolga Ceylan <tolga.ceylan AT gmail.com>:
>
>> I know this is not possible with the current code, but I was wondering
>> if anybody worked on this in the past.
>>
>> How hard would it be to add async support to freetds?
>>
>> For example, linux/epoll support?
>>
>> Cheers,
>> Tolga Ceylan
>>
>
> Hi,
> different libraries have different ideas for async implementations. What
> do you mean by async with linux/epoll? Which library are you using?
>
> Regards,
> Frediano
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
-
[freetds] freetds async usage,
Tolga Ceylan, 11/07/2014
-
Re: [freetds] freetds async usage,
Frediano Ziglio, 11/10/2014
-
Re: [freetds] freetds async usage,
Tolga Ceylan, 11/10/2014
-
Re: [freetds] freetds async usage,
Marc Abramowitz, 11/10/2014
-
Re: [freetds] freetds async usage,
Tolga Ceylan, 11/10/2014
- Re: [freetds] freetds async usage, Frediano Ziglio, 11/11/2014
-
Re: [freetds] freetds async usage,
Tolga Ceylan, 11/10/2014
-
Re: [freetds] freetds async usage,
Marc Abramowitz, 11/10/2014
-
Re: [freetds] freetds async usage,
Tolga Ceylan, 11/10/2014
-
Re: [freetds] freetds async usage,
Frediano Ziglio, 11/10/2014
Archive powered by MHonArc 2.6.24.