Received: with ECARTIS (v1.0.0; list gopher); Thu, 28 Aug 2003 14:15:49 -0500 (CDT) Return-Path: <jgoerzen@excelhustler.com> X-Original-To: gopher@complete.org Delivered-To: gopher@complete.org Received: from localhost (localhost [127.0.0.1]) by gesundheit.complete.org (Postfix) with ESMTP id 5B3F218320DD; Thu, 28 Aug 2003 14:15:48 -0500 (CDT) Received: from gatekeeper.elmer.external.excelhustler.com (gatekeeper.excelhustler.com [68.99.114.105]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "gatekeeper.elmer.external.excelhustler.com", Issuer "excelhustler.com" (not verified)) by gesundheit.complete.org (Postfix) with ESMTP id 8D7D118320D4; Thu, 28 Aug 2003 14:15:46 -0500 (CDT) Received: from chatterbox.elmer.internal.excelhustler.com (unknown [192.168.0.12]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "chatterbox.elmer.internal.excelhustler.com", Issuer "excelhustler.com" (verified OK)) by gatekeeper.elmer.external.excelhustler.com (Postfix) with ESMTP id 55CD8E0169; Thu, 28 Aug 2003 14:15:41 -0500 (CDT) Received: by chatterbox.elmer.internal.excelhustler.com (Postfix, from userid 102) id F238F5C0C6; Thu, 28 Aug 2003 14:15:40 -0500 (CDT) X-Scanned-By: AMaViS-ng/clamscan at chatterbox.elmer.internal.excelhustler.com Received: from wile.internal.excelhustler.com (wile.internal.excelhustler.com [192.168.1.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by chatterbox.elmer.internal.excelhustler.com (Postfix) with ESMTP id 682C25C0C5; Thu, 28 Aug 2003 14:15:37 -0500 (CDT) Received: by wile.internal.excelhustler.com (Postfix, from userid 1000) id 2B0BE7817; Thu, 28 Aug 2003 14:15:37 -0500 (CDT) Date: Thu, 28 Aug 2003 14:15:37 -0500 From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Subject: [gopher] Re: pygopherd & ASK Message-ID: <20030828191537.GC13821@wile.excelhustler.com> References: <20030828184443.GA17767@pippuri.mawhrin.net> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030828184443.GA17767@pippuri.mawhrin.net> User-Agent: Mutt/1.4i X-Scanned-By: clamscan at complete.org Content-Transfer-Encoding: 8bit X-archive-position: 816 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org 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

On Thu, Aug 28, 2003 at 09:44:43PM +0300, Alexey Vyskubov wrote: > I'm sorry if I'm asking a stupid questions, but I was not able to find an > answer myself. > > 1. I wonder if it is possible to use ASK with pygopherd. If it is possible > can someone give me an example of creating menu item with ASK and using > entered information afterwards?

Yes and no. PyGopherd is capable of presenting ASK blocks to a client, but is not capable of processing the results itself (the Gopher+ handler does not support datablocks coming in from the client.)

This was never really an issue because only one client has ever supported them, and that is UMN gopher, so they are not terribly versatile.

If you want that support, it would not be too hard to add.

> 2. Why if I set up VIEWS in pyg module for an entry I see this view > duplicated in gopher client?

Can you post your PYG code for me to take a look at? Can I assume you are using UMN gopher as the client? (All the other protocols will ignore +VIEWS since they do not support them.)

As a matter of fact, I wrote all that code so long ago I'll have to go back and double-check it.

> 3. Is it possible to use few views for an item?

PyGopherd does support +VIEWS. It will return a view selection to your Pyg as the searchrequest (protocol.searchrequest).

PyGopherd does *NOT* support automatically generating multiple views based on the contents of a directory and selecting the appropriate file when the request comes in. But then, I removed this from UMN gopherd some time back too, since it is really broken and has lots of side-effects.

In short, PyGopherd provides you with the framework and tools to support +VIEWS in PYG modules you write, but does not ship with any modules that use them.

> P.S. I tried to patch pygopherd to add '?' after port instead of '+' if > entry.gopherpsupport is 2; and then in pyg module using > entry.setea('ASK',...). I managed to get my question on screen in my > gopher client but afterwards I get an empty screen. It seems that > 'write' method of entry is called, but I see nothing I write there on > screen (it works if I'm not using ASK form).

I didn't follow this paragraph, could you be a little more precise? (Which file were you patching, etc.)