X-Original-To: pgsql-hackers@postgreSQL.org
Received: from spampd.localdomain (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP
	id 1F51947592C; Thu, 10 Apr 2003 12:56:51 -0400 (EDT)
Received: from fuji.krosing.net (sein.itera.ee [194.126.109.126])
	by postgresql.org (Postfix) with ESMTP
	id 21A5D474E42; Thu, 10 Apr 2003 12:56:49 -0400 (EDT)
Received: from fuji.krosing.net (lo [127.0.0.1])
	by fuji.krosing.net (8.12.8/8.12.8) with ESMTP id h3AGtI5W003485;
	Thu, 10 Apr 2003 19:55:18 +0300
Received: (from hannu@localhost)
	by fuji.krosing.net (8.12.8/8.12.8/Submit) id h3AGtI3S003483;
	Thu, 10 Apr 2003 19:55:18 +0300
X-Authentication-Warning: fuji.krosing.net: hannu set sender to hannu@tm.ee
	using -f
Subject: Re: More thoughts about FE/BE protocol
From: Hannu Krosing <hannu@tm.ee>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Galbavy <peter.galbavy@knowtion.net>,
	pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org
In-Reply-To: <1049993435.1886.24.camel@fuji.krosing.net>
References: <10478.1049927451@sss.pgh.pa.us>
	<003f01c2ff40$9f1a0e70$7c28a8c0@cblan.mblox.com>
	<3625.1049983061@sss.pgh.pa.us>
	<1049993435.1886.24.camel@fuji.krosing.net>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: 
Message-Id: <1049993718.1886.27.camel@fuji.krosing.net>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4 
Date: 10 Apr 2003 19:55:18 +0300
X-Spam-Status: No, hits=-32.9 required=5.0
	tests=BAYES_10,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	REPLY_WITH_QUOTES,USER_AGENT_XIMIAN,X_AUTH_WARNING
	autolearn=ham	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
X-Archive-Number: 200304/333
X-Sequence-Number: 37823

Hannu Krosing kirjutas N, 10.04.2003 kell 19:50:

> I would propose something like X11 protocol (from memory)
> 
> each request (query) has a serial number.
> 
> eash response is sent in resonable sized chunks, and each chunk has a
> serial number of request, chunk number of response and an indicator for
> EndOfResponse (or perhaps to for Completed or Aborted).

They should both have size as well, as Tom suggested.

> This would make resyncing easier as you can safely ignore responsed you
> dont wan't to see anymore even if for some reasons some of them are
> still in pipeline.
> 
> What could be useful (and is often requested) is sending the number of
> records in response *if it is known without extra work*.
> 
> Also there should be a way to tell the backend not to send some types of
> notices/warnings.

-----------------
Hannu