Re: [gopher] Updated Gopher RFC
> I have to say that when I suggested updating the RFC I wasn't suggesting we
> *change* anything--I was merely suggesting that we put everything together
> in one place. However, I seem to have brought up several major debates. I
> won't take a side in the mime item type, as I don't know enough about it.
> However, the period is a consistent source of confusion and debate. I would
> suggest the following solution:
> * Servers *may* send the period; clients *must* accept it
Yes.
> * Servers *should* send the period after menus, but may choose whether they
> want to send it after other files
I'm not sure if even this is necessary but I don't object to it.
> * Clients should display the period at the end of menus, if sent, to notify
> the user that this is the end of the menu
Why? With a GUI client, isn't it obvious where the end is?
> * Clients should not include the period in other output, in case that
> output has some significance which the period may disrupt.
Yes.
> * Clients should only consider a period as significant if it occurs
> immediately before the connection is terminated.
Well, let's say . and any number of \r \n.
--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
-- Helmet: But when will Now be Then?!?! Sandurz: Soon. -- "Spaceballs" -------
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Reply to: