freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: Michael Peppler <mpeppler AT peppler.org>
- To: "TDS Development Group" <freetds AT franklin.oit.unc.edu>
- Subject: Re: Which API for event-driven interfaces?
- Date: Fri, 16 Nov 2001 08:06:21 -0800
Please read the Client Library manuals regarding async programming -
if at all possible that's what FreeTDS should implement if it wants to
stay true to the Sybase API.
Michael
James Cameron writes:
> When programming event driven GUIs such as GTK+, programmers generally
> avoid threads and prefer the underlying APIs to support an event driven
> model; submit a query, wait for file descriptor to be readable using
> select().
>
> Of the interfaces provided in FreeTDS, which of them are appropriate?
>
> Requirements:
> - can submit query separate to obtaining result set,
> - exposes a file descriptor of a socket on which data is to arrive,
> - can know for certain when a query is complete.
>
> --
> James Cameron
>
> ---
> You are currently subscribed to freetds as: [mpeppler AT peppler.org]
> To unsubscribe, forward this message to $subst('Email.Unsub')
--
Michael Peppler - Data Migrations Inc. - http://www.mbay.net/~mpeppler
mpeppler AT peppler.org - mpeppler AT mbay.net
International Sybase User Group - http://www.isug.com
-
Which API for event-driven interfaces?,
James Cameron, 11/15/2001
- <Possible follow-up(s)>
- Re: Which API for event-driven interfaces?, Brian Bruns, 11/16/2001
- Re: Which API for event-driven interfaces?, Michael Peppler, 11/16/2001
Archive powered by MHonArc 2.6.24.