Received: with ECARTIS (v1.0.0; list gopher); Mon, 04 Nov 2002 15:26:49 -0500 (EST) Return-Path: <wzk@happy-ent.de> Delivered-To: gopher@complete.org Received: from um1b.pce.de (um1b.pce.de [213.185.64.7]) by gesundheit.complete.org (Postfix) with ESMTP id 7D89D645BE for <gopher@complete.org>; Mon, 4 Nov 2002 15:26:47 -0500 (EST) Received: from happy-ent.de (ppp-huerth-53.pce-net-line.de [213.185.65.181]) by um1b.pce.de (8.9.3/8.9.3) with ESMTP id VAA01359 for <gopher@complete.org>; Mon, 4 Nov 2002 21:26:43 +0100 Received: from wzk (helo=localhost) by happy-ent.de with local-esmtp (Exim 4.02) id 188rEG-00004X-00 for gopher@complete.org; Tue, 05 Nov 2002 01:06:00 +0100 Date: Tue, 5 Nov 2002 01:06:00 +0100 (CET) From: wzk@happy-ent.de To: gopher@complete.org Subject: [gopher] Re: Gopher+ Uploading Message-ID: <Pine.LNX.4.44.0211050102490.277-100000@carina.happy-ent.de> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-archive-position: 709 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: wzk@happy-ent.de Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-ID: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

Hello,

the e-mail configuration of my brand new linux computer wasn't as good as I thought. However, a quick talk to my provider gave me the (hopefully) right hint.

---------- Forwarded message ---------- Date: Sat, 2 Nov 2002 02:00:47 +0100 (CET) From: wzk@happy-ent.de To: gopher@complete.org Subject: Re: [gopher] Gopher+ Uploading

Hello Timm,

nice proposal, but (you expected it) I have some comments.

1. The client should tell the server the suggested gopher type of the uploaded file. The server can act with this information as with the other, use or ignore (and override) it.

2. The server should send a final response after the file has been uploaded (this implies that a filesize of -2 as upload parameter can not be used). I suggest three types of responses. Each response is formatted like a gopher directory entry:

3Error processing upload

to signal an error,

iUpload accepted

to tell the client that the upload is ok, and the full item's gopher directory entry

<type>\t<title>\t<selector>\t<server>\t<port>

to tell the client that everything is ok and to give him the location of the file.

In case the upload is ok the server may choose if it sends only the basic `i'-ok or the whole directory entry. The latter assumes that the server has processed the upload completly which may not be always true.

Regards

Wolfgang Zekoll