Complete.Org: Mailing Lists: Archives: gopher: November 2002:
[gopher] Re: Gopher+ Uploading

[gopher] Re: Gopher+ Uploading

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Gopher+ Uploading
From: wzk@xxxxxxxxxxxx
Date: Tue, 5 Nov 2002 01:06:00 +0100 (CET)
Reply-to: gopher@xxxxxxxxxxxx


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@xxxxxxxxxxxx
To: gopher@xxxxxxxxxxxx
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


     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.


Wolfgang Zekoll

[Prev in Thread] Current Thread [Next in Thread]