Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2] (may be
	forged)) by hub.org (8.9.3/8.9.3) with ESMTP id KAA86311
	for <pgsql-interfaces@hub.org>; Fri, 23 Jul 1999 10:06:48 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA14433;
	Fri, 23 Jul 1999 10:05:36 -0400 (EDT)
To: colin@field.medicine.adelaide.edu.au
cc: pgsql-interfaces@hub.org
Subject: Re: [INTERFACES] New asynchronous tcl postgresql interface 
In-reply-to: Your message of Fri, 23 Jul 1999 12:19:02 +1000
	<199907230219.WAA22661@hub.org>
Date: Fri, 23 Jul 1999 10:05:36 -0400
Message-ID: <14431.932738736@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Colin McCormack <colin@field.medicine.adelaide.edu.au> writes:
> I think this is possibly a better alternative to the shipped tcl interface.

> A quick/experimental Swig-generated hack
>  with itcl wrapper classes to permit:
>  - asynchronous execution of postgresql commands,
>  - cancellation of commands in progress.

Cool.  The existing libpgtcl is certainly lacking in those areas
(although it does have pretty good asynchronous-NOTIFY support,
which I hope you borrowed).

Are you planning to bring this code & doc up to the level at which
it could become part of the standard distribution?

Since your code requires itcl and the existing library doesn't,
I foresee that not everyone will want to switch.  It might be good
to choose a name that will make it clear that this code needs itcl
(I'm thinking libpgitcl, perhaps) so that people will easily see
which is which.

			regards, tom lane